Skip to contentSkip to conversation

linux-next: wireless tree build failure

PATCH New Stephen Rothwell 2 participants 2 messages Feb 27, 2009 1 message not in the archive

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

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.

Signature · 3 lines
Cheers,
Stephen Rothwell                    [email protected]
http://www.canb.auug.org.au/~sfr/

A message that is not in the archive (sent off-list or not yet received): 20090227134411.54e99731.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org

#2 lore raw

PATCH 1/1 at76c50x-usb: use dev_name() instead of struct device.bus_id

Stephen Rothwell reported that bus_id from struct device will be removed, use dev_name() instead.

---

 drivers/net/wireless/at76c50x-usb.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
drivers/net/wireless/at76c50x-usb.c +1 -1
index cc2a267..0c02f1c 100644
@@ -2268,7 +2268,7 @@ static int at76_init_new_device(struct at76_priv *priv,
 
 	printk(KERN_INFO "%s: USB %s, MAC %s, firmware %d.%d.%d-%d\n",
 	       wiphy_name(priv->hw->wiphy),
-	       interface->dev.bus_id, mac2str(priv->mac_addr),
+	       dev_name(&interface->dev), mac2str(priv->mac_addr),
 	       priv->fw_version.major, priv->fw_version.minor,
 	       priv->fw_version.patch, priv->fw_version.build);
 	printk(KERN_INFO "%s: regulatory domain 0x%02x: %s\n",

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html