From: Linus Torvalds <torvalds@linux-foundation.org>
To: Greg KH <greg@kroah.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Adrian Bunk <bunk@stusta.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Please revert 5adc55da4a7758021bcc374904b0f8b076508a11 (PCI_MULTITHREAD_PROBE)
Date: Wed, 9 May 2007 10:09:14 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705091004270.4062@woody.linux-foundation.org> (raw)
In-Reply-To: <20070509164207.GA28633@kroah.com>
On Wed, 9 May 2007, Greg KH wrote:
>
> Why is it dead? Since when is PCI the only bus in the system?
Quite frankly, any probing strategy that isn't relevant to PCI simply
isn't relevant - full stop!
No, it's not the only bus, but if something isn't relevant to PCI it
shouldn't be in any general bus layer abstraction. PCI is _that_ dominant
(and all the modern variations are just extensions on PCI, PCI didn't go
away just because it's called PCI-X or whatever).
I think buses like SCSI, USB etc are valid things to worry about as being
very different from PCI, but they are not something that the generic bus
probing code (as exemplified by the commit in question) should know/care
about. Whatever probing semantics that a SCSI adapter ends up using for
probing its bus should be up to the SCSI layer, and there is no point in
thinking that it should be a "generic bus" abstraction.
In fact, different SCSI adapters would likely have different rules. iSCSI
probably won't have anything in common with "normal" SCSI when it comes to
probing, for example.
Linus
next prev parent reply other threads:[~2007-05-09 17:10 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 13:37 Cornelia Huck
2007-05-08 14:07 ` Greg KH
2007-05-08 20:58 ` David Miller
2007-05-09 9:44 ` Greg KH
2007-05-09 17:21 ` Linus Torvalds
2007-05-08 14:11 ` Adrian Bunk
2007-05-08 14:41 ` Cornelia Huck
2007-05-08 15:27 ` Linus Torvalds
2007-05-08 16:38 ` Cornelia Huck
2007-05-08 16:47 ` david
2007-05-08 21:45 ` Stefan Richter
2007-05-08 18:30 ` Linus Torvalds
2007-05-08 19:21 ` Cornelia Huck
2007-05-08 19:31 ` Linus Torvalds
2007-05-08 20:01 ` Linus Torvalds
2007-05-08 20:26 ` david
2007-05-09 7:58 ` Cornelia Huck
2007-05-09 8:33 ` david
2007-05-09 9:15 ` Cornelia Huck
2007-05-09 9:25 ` david
2007-05-09 13:20 ` Cornelia Huck
2007-05-09 16:18 ` david
2007-05-09 17:07 ` Cornelia Huck
2007-05-09 17:09 ` david
2007-05-09 17:48 ` Cornelia Huck
2007-05-09 17:53 ` david
2007-05-09 18:36 ` Cornelia Huck
2007-05-09 18:52 ` david
2007-05-10 7:38 ` Cornelia Huck
2007-05-09 17:07 ` Greg KH
2007-05-09 17:25 ` Linus Torvalds
2007-05-09 9:30 ` Stefan Richter
2007-05-09 22:21 ` Phillip Susi
2007-05-09 22:37 ` Stefan Richter
2007-05-10 14:23 ` Phillip Susi
2007-05-10 14:55 ` Stefan Richter
2007-05-11 7:22 ` Cornelia Huck
2007-05-08 20:51 ` Cornelia Huck
2007-05-08 21:41 ` David Miller
2007-05-09 9:55 ` Greg KH
2007-05-09 8:14 ` Duncan Sands
2007-05-09 8:45 ` Cornelia Huck
2007-05-09 9:16 ` Duncan Sands
2007-05-09 12:37 ` Cornelia Huck
2007-05-08 20:36 ` Cornelia Huck
2007-05-09 9:53 ` Greg KH
2007-05-09 13:38 ` Cornelia Huck
2007-05-09 16:42 ` Greg KH
2007-05-09 16:50 ` david
2007-05-09 17:14 ` Cornelia Huck
2007-05-09 17:09 ` Linus Torvalds [this message]
2007-05-08 21:15 ` David Miller
2007-05-08 22:19 ` Stefan Richter
2007-05-09 9:46 ` Greg KH
2007-05-08 15:15 ` Linus Torvalds
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=alpine.LFD.0.98.0705091004270.4062@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=cornelia.huck@de.ibm.com \
--cc=greg@kroah.com \
--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
all inboxes | Powered by JetHome®