From: Matthew Wilcox <matthew@wil.cx>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Greg KH <greg@kroah.com>, Joel Becker <joel.becker@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
"Linux-iSCSI.org Target Dev"
<linux-iscsi-target-dev@googlegroups.com>,
SCST-Devel <scst-devel@lists.sourceforge.net>,
Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] [ConfigFS]: Allow symbolic links from a SysFS struct kobject source.
Date: Fri, 17 Oct 2008 05:32:52 -0600 [thread overview]
Message-ID: <20081017113252.GV15064@parisc-linux.org> (raw)
In-Reply-To: <1224231739.5556.303.camel@haakon2.linux-iscsi.org>
On Fri, Oct 17, 2008 at 01:22:18AM -0700, Nicholas A. Bellinger wrote:
> This of course means that non TYPE_DISK of struct scsi_device would need
> to appear under /sys/ to be referenced using the symlink method.. I
> know that drivers/scsi/sr.c currently does not show up under /sys..
Hmm?
$ ls -l /sys/block/sr0/
total 0
lrwxrwxrwx 1 root root 0 2008-10-17 07:30 bdi -> ../../class/bdi/11:0
-r--r--r-- 1 root root 4096 2008-10-17 07:30 capability
-r--r--r-- 1 root root 4096 2008-10-17 07:30 dev
lrwxrwxrwx 1 root root 0 2008-10-17 07:30 device -> ../../devices/pci0000:00/0000:00:1f.1/host3/target3:0:0/3:0:0:0
drwxr-xr-x 2 root root 0 2008-10-17 07:30 holders
drwxr-xr-x 2 root root 0 2008-10-17 07:30 power
drwxr-xr-x 3 root root 0 2008-10-17 07:30 queue
-r--r--r-- 1 root root 4096 2008-10-17 07:30 range
-r--r--r-- 1 root root 4096 2008-10-17 07:30 removable
-r--r--r-- 1 root root 4096 2008-10-17 07:30 ro
-r--r--r-- 1 root root 4096 2008-10-17 07:30 size
drwxr-xr-x 2 root root 0 2008-10-17 07:30 slaves
-r--r--r-- 1 root root 4096 2008-10-17 07:30 stat
lrwxrwxrwx 1 root root 0 2008-10-17 07:30 subsystem -> ../../block
-rw-r--r-- 1 root root 4096 2008-10-17 07:30 uevent
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-10-17 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 6:55 [PATCH] [ConfigFS]: Allow symbolic links from a SysFS struct kobject source Nicholas A. Bellinger
2008-10-17 7:44 ` Greg KH
2008-10-17 8:22 ` Nicholas A. Bellinger
2008-10-17 11:32 ` Matthew Wilcox [this message]
2008-10-17 19:02 ` Nicholas A. Bellinger
2008-10-17 17:39 ` Greg KH
2008-10-17 19:19 ` Nicholas A. Bellinger
2008-10-17 20:10 ` Greg KH
2008-10-18 2:41 ` Nicholas A. Bellinger
2008-10-17 19:48 ` Joel Becker
2008-10-17 20:03 ` Nicholas A. Bellinger
2008-10-17 20:07 ` Nicholas A. Bellinger
2008-10-17 19:39 ` Joel Becker
2008-10-17 19:50 ` Nicholas A. Bellinger
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=20081017113252.GV15064@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=joel.becker@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-iscsi-target-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=scst-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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.