From: Greg KH <greg@kroah.com>
To: Byron Stanoszek <gandalf@winds.org>
Cc: linux-usb-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] Make USB process hub events in correct order
Date: Tue, 15 Jun 2004 13:06:34 -0700 [thread overview]
Message-ID: <20040615200634.GA19411@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0406151412430.26219@winds.org>
On Tue, Jun 15, 2004 at 02:26:49PM -0400, Byron Stanoszek wrote:
> This patch fixes the USB hub module to process events in the order that they
> are received. It fixes the case where multi-port devices have multiple
> hubs in them--while they are detected in the correct order, they are
> initialized in reverse. It is required for the Sealink 8-port USB->serial
> hubs
> to initialize with the port numbers in the correct order.
>
> I don't think it breaks any existing functionality, but I won't send this to
> Linus yet till I know it doesn't break anything.
Linus isn't the person to send this to :)
> Patch below against 2.6.7-rc3.
You know you still can't rely on the events happening in "numerical"
order, even with this patch, right?
That's what tools like udev is for, that way you can always name your
/dev/ttyUSB* devices properly.
Anyway, I don't have a problem with this patch, other than it doesn't
apply to the current USB tree, as there has been a lot of work in the
hub driver recently. Care to make it up again against the latest -mm
release, as that has the USB development tree included in it.
thanks,
greg k-h
prev parent reply other threads:[~2004-06-15 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 18:26 [PATCH] Make USB process hub events in correct order Byron Stanoszek
2004-06-15 20:06 ` Greg KH [this message]
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=20040615200634.GA19411@kroah.com \
--to=greg@kroah.com \
--cc=gandalf@winds.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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.