From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Olaf Hering <olh@suse.de>, Paul Mackeras <paulus@samba.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: scsi proc_info called unconditionally
Date: 17 Aug 2003 10:56:17 +0100 [thread overview]
Message-ID: <1061114176.21502.11.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <20030817103914.A26579@infradead.org>
On Sul, 2003-08-17 at 10:39, Christoph Hellwig wrote:
> No! proc_info is deprecated in 2.6 and you should not add a new
> implementation. If you want to expose information to userland
> use sysfs.
It probably should give the driver name and version. Christoph is
right in the longer term but in the real world people still expect
/proc/scsi/* to contain at least that info.
Possibly for 2.7.x /proc/scsi/* should become an fs or entirely sysfs
next prev parent reply other threads:[~2003-08-17 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-16 8:44 scsi proc_info called unconditionally Olaf Hering
2003-08-16 10:06 ` Christoph Hellwig
2003-08-16 17:00 ` Alan Cox
2003-08-17 8:09 ` Olaf Hering
2003-08-17 9:39 ` Christoph Hellwig
2003-08-17 9:56 ` Alan Cox [this message]
2003-08-17 10:07 ` Christoph Hellwig
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=1061114176.21502.11.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.de \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).