The patch titled vt6655: fix build when !CONFIG_WIRELESS_EXT has been removed from the -mm tree. Its filename was vt6655-fix-build-when-config_wireless_ext.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: vt6655: fix build when !CONFIG_WIRELESS_EXT From: Alexander Beregalov <a.beregalov@xxxxxxxxx> Fix this build error when CONFIG_WIRELESS_EXT is not set: drivers/staging/vt6655/device_main.c:1153: error: 'struct net_device' has no member named 'wireless_handlers' Cc: Forest Bond <forest@xxxxxxxxxxxxxxxxxxx> Signed-off-by: Alexander Beregalov <a.beregalov@xxxxxxxxx> Cc: Greg KH <greg@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/staging/vt6655/device_main.c | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff -puN drivers/staging/vt6655/device_main.c~vt6655-fix-build-when-config_wireless_ext drivers/staging/vt6655/device_main.c --- a/drivers/staging/vt6655/device_main.c~vt6655-fix-build-when-config_wireless_ext +++ a/drivers/staging/vt6655/device_main.c @@ -1146,14 +1146,9 @@ device_found1(struct pci_dev *pcid, cons dev->irq = pcid->irq; dev->netdev_ops = &device_netdev_ops; -#ifdef WIRELESS_EXT -//Einsn Modify for ubuntu-7.04 -// dev->wireless_handlers->get_wireless_stats = iwctl_get_wireless_stats; -#if WIRELESS_EXT > 12 +#ifdef CONFIG_WIRELESS_EXT dev->wireless_handlers = (struct iw_handler_def *)&iwctl_handler_def; -// netdev->wireless_handlers = NULL; -#endif /* WIRELESS_EXT > 12 */ -#endif /* WIRELESS_EXT */ +#endif rc = register_netdev(dev); if (rc) _ Patches currently in -mm which might be from a.beregalov@xxxxxxxxx are linux-next.patch vt6655-s-void-void.patch staging-otus-remove-dependency-on-wireless_ext-version.patch staging-rt2860-remove-dependency-on-wireless_ext-version.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html