From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Multiprobe sanitizer
Date: Thu, 17 Aug 2006 05:00:13 -0700 [thread overview]
Message-ID: <20060817120013.GC6843@kroah.com> (raw)
In-Reply-To: <1155806676.11312.175.camel@localhost.localdomain>
On Thu, Aug 17, 2006 at 11:24:35AM +0200, Benjamin Herrenschmidt wrote:
> Probe ordering is fragile and completely defeated with busses that are
> already probed asynchronously (like USB or firewire), and things can
> only get worse. Thus we need to look for generic solutions, the trick of
> maintaining probe ordering will work around problems today but we'll
> still hit the wall in an increasing number of cases in the future.
That's exactly why udev was created :)
It can handle bus ordering issues already today just fine, and distros
use it this way in shipping, "enterprise ready" products.
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-17 12:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 16:42 PATCH: Multiprobe sanitizer Alan Cox
2006-08-16 22:26 ` Greg KH
2006-08-17 0:36 ` Alan Cox
2006-08-17 6:57 ` Benjamin Herrenschmidt
2006-08-17 7:00 ` Arjan van de Ven
2006-08-17 8:41 ` Alan Cox
2006-08-17 9:24 ` Benjamin Herrenschmidt
2006-08-17 12:00 ` Greg KH [this message]
2006-08-17 12:12 ` Benjamin Herrenschmidt
2006-08-17 12:22 ` Greg KH
2006-08-17 12:37 ` Benjamin Herrenschmidt
2006-08-17 13:04 ` Arjan van de Ven
2006-08-17 13:10 ` Benjamin Herrenschmidt
2006-08-17 15:44 ` Greg KH
2006-08-17 14:43 ` Olaf Hering
2006-08-17 15:42 ` Greg KH
2006-08-17 11:58 ` Greg KH
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=20060817120013.GC6843@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox