All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: David Vrabel <david.vrabel@csr.com>
Cc: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
	linux-usb <linux-usb@vger.kernel.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Dropping WUSB/UWB from my patch queue
Date: Tue, 15 Jul 2008 22:49:11 -0700	[thread overview]
Message-ID: <20080716054911.GA9806@kroah.com> (raw)
In-Reply-To: <487CE2E7.90505@csr.com>

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

  parent reply	other threads:[~2008-07-16  6:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 18:00 Dropping WUSB/UWB from my patch queue Greg KH
2008-07-07 10:03 ` David Vrabel
2008-07-15 15:53   ` Greg KH
2008-07-15 17:48     ` David Vrabel
2008-07-15 18:36       ` Perez-Gonzalez, Inaky
2008-07-16  5:49       ` Greg KH [this message]
2008-07-16  9:52         ` David Vrabel
2008-07-16 16:20           ` Perez-Gonzalez, Inaky
2008-07-16 16:23             ` Greg KH
2008-07-16 17:35             ` David Vrabel
2008-07-16 17:55               ` Perez-Gonzalez, Inaky

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=20080716054911.GA9806@kroah.com \
    --to=greg@kroah.com \
    --cc=david.vrabel@csr.com \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.