From: Luben Tuikov <ltuikov@yahoo.com>
To: linux-scsi <linux-scsi@vger.kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ide <linux-ide@vger.kernel.org>,
"Accardi, Kristen C" <kristen.c.accardi@intel.com>
Subject: Re: [PATCH] enclosure: add support for enclosure services
Date: Mon, 4 Feb 2008 16:32:18 -0800 (PST) [thread overview]
Message-ID: <50030.21278.qm@web31808.mail.mud.yahoo.com> (raw)
In-Reply-To: <1202074856.3318.111.camel@localhost.localdomain>
--- On Sun, 2/3/08, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> The enclosure misc device is really just a library providing
> sysfs
> support for physical enclosure devices and their
> components.
Who is the target audience/user of those facilities?
a) The kernel itself needing to read/write SES pages?
b) A user space application using sysfs to read/write
SES pages?
At the moment SES device management is done via
an application (user-space) and a user-space library
used by the application and /dev/sgX to send SCSI
commands to the SES device.
One could have a very good argument to not bloat
the kernel with this but leave it to a user-space
application and a library to do all this and
communicate with the SES device via the kernel's /dev/sgX.
Luben
next prev parent reply other threads:[~2008-02-05 0:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 21:40 [PATCH] enclosure: add support for enclosure services James Bottomley
2008-02-03 22:03 ` Sam Ravnborg
2008-02-04 0:16 ` James Bottomley
2008-02-06 0:12 ` Andrew Morton
2008-02-06 2:57 ` James Bottomley
2008-02-05 0:32 ` Luben Tuikov [this message]
2008-02-05 0:41 ` James Bottomley
2008-02-05 2:01 ` Luben Tuikov
2008-02-05 2:14 ` James Bottomley
2008-02-05 3:28 ` Luben Tuikov
2008-02-05 4:37 ` James Bottomley
2008-02-05 5:35 ` Luben Tuikov
2008-02-05 15:01 ` James Bottomley
2008-02-05 19:33 ` Luben Tuikov
2008-02-05 20:29 ` James Bottomley
2008-02-05 20:39 ` Luben Tuikov
2008-02-12 18:22 ` Kristen Carlson Accardi
2008-02-12 18:45 ` James Bottomley
2008-02-12 19:07 ` Kristen Carlson Accardi
2008-02-12 19:28 ` James Bottomley
2008-02-13 17:45 ` Kristen Carlson Accardi
2008-02-13 18:17 ` James Bottomley
2008-02-16 12:44 ` Pavel Machek
2008-02-13 9:48 ` Luben Tuikov
2008-02-13 14:08 ` James Smart
2008-02-13 16:04 ` James Bottomley
2008-02-13 16:22 ` James Smart
2008-02-13 16:43 ` James Bottomley
2008-02-13 16:49 ` James Smart
2008-02-12 19:45 ` Luben Tuikov
-- strict thread matches above, loose matches on Subject: below --
2008-02-13 11:15 Luben Tuikov
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=50030.21278.qm@web31808.mail.mud.yahoo.com \
--to=ltuikov@yahoo.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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