Re: Dropping WUSB/UWB from my patch queue

From: Greg KH
Date: Wed Jul 16 2008 - 02:06:52 EST


On Tue, Jul 15, 2008 at 06:48:23PM +0100, David Vrabel wrote:
> Greg KH wrote:
> > On Mon, Jul 07, 2008 at 11:03:28AM +0100, David Vrabel wrote:
> >> Greg KH wrote:
> >>> Hi David,
> >
> >>> In looking further at the WUSB/UWB code, it doesn't look like it is
> >>> going to make it for the 2.6.27 kernel tree due to the reliance on some
> >>> contriversial core USB changes as well as a total lack of documentation
> >>> for the sysfs apis.
> >> I assume you are referring to the usb_dev_reset_delayed() change here.
> >> This is only required by the wire adapter code and should not prevent
> >> the majority of the UWB and WUSB stack from being merged.
> >
> > Ok, thanks for letting me know, I did not realize this.
> >
> >> You should postpone:
> >>
> >> usb-add-usb_dev_reset_delayed.patch
> >> wusb-add-the-wire-adapter-core.patch
> >> wusb-add-hwa-hc-wireless-host-controller-driver.patch
> >> wusb-wa-abort-rpipe-request-type-fix.patch
>
> I took another look at where usb_dev_reset_delayed() is used and there
> are more places. You will also need to postpone:
>
> uwb/uwb-add-hwa-rc-radio-controller-driver.patch
> uwb/uwb-i1480-driver.patch
> uwb/uwb-i1480-wlp-driver.patch
> uwb/uwb-disable-command-event-filtering-for-DUB-1210.patch
> uwb/uwb-add-intel-i1480-hwa-to-the-uwb-rc-quirk-table.patch
>
> And since there are now no drivers for WLP hardware you may also postpone:
>
> uwb/uwb-add-wimedia-llc-protocol-core.patch
> uwb/uwb-wlp-messages.patch
> uwb/uwb-wlp-wss.patch
> uwb/uwb-wlp-build-system.patch
> uwb/wusb-drivers-uwb-wlp-sysfs.c-move-misplaced-debug-statement.patch

Ugh, so, what will end up getting merged? Anything that people can
actually use? :)

I'll poke at this on Friday and see what falls out.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/