From: Andy Whitcroft <apw@shadowen.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: 2.6.18-git9
Date: Thu, 28 Sep 2006 10:23:54 +0100 [thread overview]
Message-ID: <451B94AA.3090100@shadowen.org> (raw)
I have a couple of power boxes which no longer seem to be able to
compile mainline as of 2.6.18-git9. The build fails as below:
CC drivers/usb/core/driver.o
drivers/usb/core/driver.c: In function `usb_probe_device':
drivers/usb/core/driver.c:168: error: structure has no member named
`pm_usage_cnt'
drivers/usb/core/driver.c: In function `usb_driver_claim_interface':
drivers/usb/core/driver.c:305: error: structure has no member named
`pm_mutex'
drivers/usb/core/driver.c:309: error: structure has no member named
`pm_mutex'
drivers/usb/core/driver.c: In function `usb_driver_release_interface':
drivers/usb/core/driver.c:358: error: structure has no member named
`pm_mutex'
drivers/usb/core/driver.c:362: error: structure has no member named
`pm_mutex'
make[3]: *** [drivers/usb/core/driver.o] Error 1
make[2]: *** [drivers/usb/core] Error 2
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2
This seems to be realated to the changes in this commit:
commit 645daaab0b6adc35c1838df2a82f9d729fdb1767
usbcore: add autosuspend/autoresume infrastructure
The machines in question do not have CONFIG_PM set. It seems that the
definition of pm_mutex et al in struct usb_device are contingent on that
defined, but the use of it in usb_driver_release_interface() are not.
Its not clear to me if suspending in this context is quite the same as
full suspend to disk that I associate with PM so I am unsure which bit
is in error. Will retest with those references under CONFIG_PM.
Alan?
-apw
next reply other threads:[~2006-09-28 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 9:23 Andy Whitcroft [this message]
2006-09-28 16:04 ` 2.6.18-git9 Alan Stern
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=451B94AA.3090100@shadowen.org \
--to=apw@shadowen.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@osdl.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).