From: Edward Falk <efalk@google.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Patrick Mansfield <patmans@us.ibm.com>, linux-scsi@vger.kernel.org
Subject: Re: map gendisk (or blockdev) -> scsi_device
Date: Thu, 14 Jul 2005 15:54:52 -0700 [thread overview]
Message-ID: <42D6ED3C.8030307@google.com> (raw)
In-Reply-To: <20050714195613.GA22935@infradead.org>
Christoph Hellwig wrote:
> On Wed, Jul 13, 2005 at 04:46:54PM -0700, Patrick Mansfield wrote:
>
>>Add or use the attributes under the scsi_device, then use the
>>/sysfs/block/sd/device symlink to find the corresponding scsi_device.
>
>
> yupp, the /sys/block/* attributes are really only meant to be for
> thing related to the actual block device, not the underlying hardware.
What is the difference between "actual block device" and "underlying
hardware"?
-ed
prev parent reply other threads:[~2005-07-14 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 0:38 map gendisk (or blockdev) -> scsi_device Edward Falk
2005-07-13 1:31 ` Chen, Kenneth W
2005-07-13 14:38 ` Christoph Hellwig
2005-07-13 18:44 ` Edward Falk
2005-07-13 23:46 ` Patrick Mansfield
2005-07-14 18:38 ` Edward Falk
2005-07-14 19:56 ` Christoph Hellwig
2005-07-14 22:54 ` Edward Falk [this message]
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=42D6ED3C.8030307@google.com \
--to=efalk@google.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--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 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.