From: Greg KH <gregkh@suse.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [GIT PATCH] USB fixes for 2.6.20-rc5
Date: Mon, 22 Jan 2007 12:23:44 -0800 [thread overview]
Message-ID: <20070122202344.GA10579@suse.de> (raw)
In-Reply-To: <1169496904.27023.11.camel@violet>
On Mon, Jan 22, 2007 at 09:15:04PM +0100, Marcel Holtmann wrote:
> Hi Greg,
>
> > They include a small number of fixes for some USB bugs, and some new
> > device ids, all of the details are below. I've also disabled the USB
> > multithreaded probe option, as it broke a number of people's machines.
>
> what about the two pending patches to make device_move() working as
> expected. The current implementation is broken and basically useless.
I don't feel comfortable adding them to the 2.6.20 kernel at this late
period, for a variety of reasons. I really want them to be tested out
in the -mm tree and then in the full -rc series due to the fact that
they are non-trivial, and touch the driver core code that everyone uses,
not just that function.
Also, it's a new feature (reparent back to the original parent), not
necessarily a bugfix.
And yes, I realize that the functions don't work fully right now, but as
long as you don't want to re-parent the devices, they should work,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2007-01-22 20:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 20:07 [GIT PATCH] USB fixes for 2.6.20-rc5 Greg KH
2007-01-22 20:15 ` [linux-usb-devel] " Marcel Holtmann
2007-01-22 20:23 ` Greg KH [this message]
2007-01-22 20:28 ` Marcel Holtmann
2007-01-23 9:58 ` Cornelia Huck
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=20070122202344.GA10579@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox