From: Patrick Mansfield <patmans@us.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] remove scsi_device proc printing from drivers
Date: Sun, 27 Apr 2003 11:10:10 -0700 [thread overview]
Message-ID: <20030427111010.B21878@beaverton.ibm.com> (raw)
In-Reply-To: <20030427185628.A30233@lst.de>; from hch@lst.de on Sun, Apr 27, 2003 at 06:56:28PM +0200
On Sun, Apr 27, 2003 at 06:56:28PM +0200, Christoph Hellwig wrote:
> BTW, does someone have opintions on reading of /proc/scsi/scsi?
> It's just a duplication of the sysfs tree so it should probably
> go away also. OTOH there's a slightly higher chance on userland
> actually using this than for the LLDDs..
IMO leave it for 2.6, and remove /proc/scsi/scsi read (and maybe writes,
if we have sysfs replacement in 2.6) in 2.7.
-- Patrick Mansfield
prev parent reply other threads:[~2003-04-27 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 16:56 [PATCH] remove scsi_device proc printing from drivers Christoph Hellwig
2003-04-27 18:10 ` Patrick Mansfield [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=20030427111010.B21878@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@steeleye.com \
--cc=hch@lst.de \
--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