···22# USB Monitor configuration33#4455-# In normal life, it makes little sense to have usbmon as a module, and in fact66-# it is harmful, because there is no way to autoload the module.77-# The 'm' option is allowed for hackers who debug the usbmon itself,88-# and for those who have usbcore as a module.95config USB_MON1010- tristate "USB Monitor"1111- depends on USB66+ bool "USB Monitor"77+ depends on USB!=n128 default y139 help1410 If you say Y here, a component which captures the USB traffic···1317 Harding's USBMon.14181519 This is somewhat experimental at this time, but it should be safe,1616- as long as you aren't building this as a module and then removing it.1717-1818- If unsure, say Y. Do not say M.2020+ as long as you aren't using modular USB and try to remove this2121+ module.
···290290 struct class_device *class_dev; /* class device for this bus */291291 struct kref kref; /* handles reference counting this bus */292292 void (*release)(struct usb_bus *bus); /* function to destroy this bus's memory */293293-#if defined(CONFIG_USB_MON) || defined(CONFIG_USB_MON_MODULE)293293+#if defined(CONFIG_USB_MON)294294 struct mon_bus *mon_bus; /* non-null when associated */295295 int monitored; /* non-zero when monitored */296296#endif