From: Greg KH <greg@kroah.com>
To: James Smart <James.Smart@Emulex.Com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, Tony Jones <tonyj@suse.de>
Subject: Re: [patch] convert the scsi layer to use struct device
Date: Sun, 16 Mar 2008 22:35:19 -0700 [thread overview]
Message-ID: <20080317053519.GB5229@kroah.com> (raw)
In-Reply-To: <47DDF05D.8060608@emulex.com>
On Mon, Mar 17, 2008 at 12:15:25AM -0400, James Smart wrote:
>
>
> Kay Sievers wrote:
>>> Well, the <classname> prefix came about because there was namespace
>>> overlap
>>> between different classes (e.g. scsi_host and fc_host classes use the
>>> same name,
>>> and I think where we originally saw this was in the way serial ports were
>>> enumerated
>>> for some base systems as well).
>>>
>>> So I don't see how you can kill the <classname>:<devname> names by
>>> SYSFS_DEPRECATED.
>> With SYSFS_DEPRECATED, nothing will change. But these links don't exist
>> with !SYSFS_DEPRECATED, because the class devices live in
>> subdirectories, named after the class they come from, there is no
>> namespace problem, or any problem to find these devices, you don't even
>> need readdir() to look them up.
>
> Ok, it should have read :
> I don't see how you can kill the <classname>:<devname> names w/
> !SYSFS_DEPRECATED.
>
> You still haven't answered my question about namespace overlap. What
> happens when the
> device belongs to multiple classes, and the classes have the same name for
> the class
> device ? I don't believe we ever want to be in the case where the classes
> have to
> understand a global namespace.
I take it you haven't even looked at how !SYSFS_DEPRECATED works today,
have you? Try it and you will see that the namespace issue has been
taken care of a long time ago :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-03-17 5:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 21:06 [patch] convert the scsi layer to use struct device Greg KH
2008-03-14 14:13 ` Hannes Reinecke
2008-03-14 17:15 ` James Bottomley
2008-03-14 21:20 ` James Bottomley
2008-03-14 21:58 ` Kay Sievers
2008-03-15 14:19 ` James Bottomley
2008-03-15 15:17 ` Kay Sievers
2008-03-15 16:16 ` James Bottomley
2008-03-15 18:01 ` James Bottomley
2008-03-15 18:26 ` Kay Sievers
2008-03-15 18:34 ` James Bottomley
2008-03-15 20:38 ` Stefan Richter
2008-03-15 18:04 ` Kay Sievers
2008-03-15 18:31 ` James Bottomley
2008-03-15 18:56 ` Kay Sievers
2008-03-15 19:33 ` James Bottomley
2008-03-15 19:43 ` Kay Sievers
2008-03-16 20:21 ` James Smart
2008-03-16 21:04 ` Kay Sievers
2008-03-17 4:15 ` James Smart
2008-03-17 5:35 ` Greg KH [this message]
2008-03-17 12:18 ` James Smart
2008-03-17 13:40 ` Kay Sievers
2008-03-17 13:55 ` James Bottomley
2008-03-17 17:57 ` James Bottomley
2008-03-19 0:48 ` Greg KH
2008-03-19 20:38 ` 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=20080317053519.GB5229@kroah.com \
--to=greg@kroah.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=James.Smart@Emulex.Com \
--cc=kay.sievers@vrfy.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tonyj@suse.de \
/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