From: Mike Anderson <andmike@us.ibm.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Willem Riede <wrlk@riede.org>,
Kai Makisara <Kai.Makisara@kolumbus.fi>,
linux-scsi@vger.kernel.org, Matt_Domsch@Dell.com,
Douglas Gilbert <dougg@torque.net>
Subject: Re: [PATCH / RFC] osst, st, sg sysfs removes
Date: Tue, 14 Jan 2003 10:33:14 -0800 [thread overview]
Message-ID: <20030114183314.GC1613@beaverton.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301140925160.1025-100000@localhost.localdomain>
Patrick Mochel [mochel@osdl.org] wrote:
>
> I have reservations about blindly adding a 'char' subsystem. However, I
> think it would be useful, and encourage someone to do the leg work..
That was not my intention. A char subsystem would need to have leg work
similar to what others did for block. We do not want to create a char
directory in sysfs and start populating it quickly to solve point
problems.
One point I was trying to make in previous mail was that if a char tree
follows the semantics of a block tree and creates a back link from the
device we need to consider the issue of "sg" (i.e. possible multiple
registers with the char subsystem per device) along with other devices up
front.
-andmike
--
Michael Anderson
andmike@us.ibm.com
next prev parent reply other threads:[~2003-01-14 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 22:21 [PATCH / RFC] osst, st, sg sysfs removes Mike Anderson
2003-01-11 12:25 ` Kai Makisara
2003-01-11 15:48 ` Willem Riede
2003-01-12 19:59 ` Mike Anderson
2003-01-14 15:26 ` Patrick Mochel
2003-01-14 18:33 ` Mike Anderson [this message]
2003-01-14 23:08 ` Andries Brouwer
2003-01-11 17:02 ` Mike Anderson
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=20030114183314.GC1613@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=Matt_Domsch@Dell.com \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=wrlk@riede.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