From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Greg KH <greg@kroah.com>, Patrick Mansfield <patmans@us.ibm.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: dev_printk output
Date: Sat, 20 May 2006 08:46:57 -0500 [thread overview]
Message-ID: <1148132817.3529.1.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20060520045544.GD2826@parisc-linux.org>
On Fri, 2006-05-19 at 22:55 -0600, Matthew Wilcox wrote:
> Then we still get the inconsistency of device names changing as
> drivers
> are loaded. I think we should declare it a bug for devices to not be
> on a bus. The only example I have of devices not-on-a-bus are scsi
> targets. I would propose introducing a new scsi_target bus for them,
> then removing the 'target' from the start of the bus_id. Adding them
> to
> the scsi bus looks like it'd be a lot of work.
It's not just the target. All the intermediate devices in transport
classes don't have busses either. The only reason scsi_device has a
bus is so we can use the driver model to bind the ULDs.
James
next prev parent reply other threads:[~2006-05-20 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060511150015.GJ12272@parisc-linux.org>
[not found] ` <20060512170854.GA11215@us.ibm.com>
[not found] ` <20060513050059.GR12272@parisc-linux.org>
[not found] ` <20060518183652.GM1604@parisc-linux.org>
[not found] ` <20060518200957.GA29200@us.ibm.com>
2006-05-19 20:11 ` Matthew Wilcox
2006-05-19 20:28 ` Greg KH
2006-05-20 4:55 ` Matthew Wilcox
2006-05-20 13:46 ` James Bottomley [this message]
2006-05-20 21:21 ` Greg KH
2006-05-29 3:57 ` Matthew Wilcox
2006-05-29 16:30 ` James Bottomley
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=1148132817.3529.1.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=patmans@us.ibm.com \
/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®