From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-next@vger.kernel.org, Kalle Valo <kalle.valo@iki.fi>,
Kay Sievers <kay.sievers@vrfy.org>, Greg KH <greg@kroah.com>
Subject: linux-next: wireless tree build failure
Date: Fri, 27 Feb 2009 13:44:11 +1100 [thread overview]
Message-ID: <20090227134411.54e99731.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Hi John,
Today's linux-next build (x86_64 allmodconfig) failed like this:
drivers/net/wireless/at76c50x-usb.c: In function 'at76_init_new_device':
drivers/net/wireless/at76c50x-usb.c:2271: error: 'struct device' has no member named 'bus_id'
Caused by commit 26b9886dbb1e6930a8a5df9dcf64d8dacb80597b ("at76c50x-usb:
add driver") from the wireless tree interacting with commit
d3592c7c13d14e410ffbf0e86dcd7abb3a23077f ("driver core: get rid of struct
device's bus_id string array") from the driver-core tree.
This can be fixed by using dev_name() which is already available in
Linus' tree.
I have dropped the wireless tree for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-02-27 2:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 2:44 Stephen Rothwell [this message]
[not found] ` <20090227134411.54e99731.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-02-27 5:50 ` [PATCH] at76c50x-usb: use dev_name() instead of struct device.bus_id Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2009-11-09 8:08 linux-next: wireless tree build failure Stephen Rothwell
2009-11-09 13:37 ` Bartlomiej Zolnierkiewicz
[not found] <20090505115455.0b147aeb.sfr@canb.auug.org.au>
2009-05-05 2:55 ` John W. Linville
2009-04-22 1:57 Stephen Rothwell
2009-04-22 8:59 ` Johannes Berg
2009-04-22 13:03 ` Stephen Rothwell
2009-04-22 13:06 ` John W. Linville
2009-04-22 13:33 ` Johannes Berg
2009-04-22 13:36 ` Matthew Garrett
2009-06-03 2:52 ` Stephen Rothwell
2009-06-15 12:21 ` Stephen Rothwell
2009-04-22 13:11 ` Johannes Berg
2009-04-28 3:28 ` Stephen Rothwell
2009-04-28 12:50 ` John W. Linville
2009-03-23 4:39 Stephen Rothwell
2009-03-23 4:53 ` David Miller
2009-03-23 5:01 ` Yang Hongyang
2009-03-23 4:55 ` David Miller
2009-03-23 5:06 ` Yang Hongyang
2009-03-23 5:48 ` Stephen Rothwell
2009-03-23 7:59 ` David Miller
2009-03-23 8:10 ` Stephen Rothwell
2009-02-12 8:35 Stephen Rothwell
2009-02-12 16:16 ` John W. Linville
2009-02-12 22:07 ` Stephen Rothwell
2009-02-13 18:24 ` Dave
2009-02-13 18:24 ` John W. Linville
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=20090227134411.54e99731.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=greg@kroah.com \
--cc=kalle.valo@iki.fi \
--cc=kay.sievers@vrfy.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).