LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	gregkh@suse.de, Andy Whitcroft <apw@shadowen.org>
Subject: [BUILD_FAILURE] linux-next: Tree for March 6 drivers/usb broken
Date: Thu, 06 Mar 2008 14:48:38 +0530	[thread overview]
Message-ID: <47CFB6EE.5050307@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080306162606.970aefe1.sfr@canb.auug.org.au>

The kernel build fails with error

drivers/usb/core/hub.c: In function 'persist_enabled':
drivers/usb/core/hub.c:633: error: 'struct usb_device' has no member named 'persist_enabled'
drivers/usb/core/hub.c: In function 'hub_restart':
drivers/usb/core/hub.c:719: error: 'struct usb_device' has no member named 'reset_resume'
make[3]: *** [drivers/usb/core/hub.o] Error 1
make[2]: *** [drivers/usb/core] Error 2
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2

This is introduced by persist_enabled() and # CONFIG_PM is not set
-- 
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.

  parent reply	other threads:[~2008-03-06  9:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06  5:26 linux-next: Tree for March 6 Stephen Rothwell
2008-03-06  9:07 ` Andy Whitcroft
2008-03-06 11:50   ` Stephen Rothwell
2008-03-07  2:10     ` Stephen Rothwell
2008-03-06  9:18 ` Kamalesh Babulal [this message]
2008-03-06 12:10   ` [BUILD_FAILURE] linux-next: Tree for March 6 drivers/usb broken Stephen Rothwell
2008-03-06 13:35 ` [BUILD_FAILURE] linux-next: Tree for March 6 build failure Kamalesh Babulal
2008-03-06 19:12   ` David Miller
2008-03-07  7:44     ` Kamalesh Babulal
2008-03-07 19:12       ` David Miller
2008-03-09  8:39 ` linux-next: Tree for March 6: acpi_os_wait_semaphore tries to register non-static key Laurent Riffard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47CFB6EE.5050307@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=apw@shadowen.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: [BUILD_FAILURE] linux-next: Tree for March 6 drivers/usb broken' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).