public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Higdon <jeremy@sgi.com>
To: Christoph Hellwig <hch@infradead.org>,
	Hannes Reinecke <hare@suse.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Use proper seq_file api for /proc/scsi/scsi
Date: Fri, 8 Apr 2005 00:23:46 -0700	[thread overview]
Message-ID: <20050408072345.GA1018765@sgi.com> (raw)
In-Reply-To: <20050407112412.GA12072@infradead.org>

On Thu, Apr 07, 2005 at 12:24:12PM +0100, Christoph Hellwig wrote:
> On Thu, Apr 07, 2005 at 01:21:23PM +0200, Hannes Reinecke wrote:
> > > /proc/scsi/scsi is deprecated and even only compiled in if
> > > "legacy /proc/scsi/ support" is enabled.  Please move over to lssci which
> > > is using sysfs ASAP.
> > > 
> > Ah. And that's enough reason for it not to work properly?
> > Deprecated as it may be, but one could at least expect it to _work_.
> 
> It works for those setups that already worked with 2.4.x, aka only a few
> luns.

Even if it's deprecated, wouldn't it be good to fix it as long as
it's there, unless it hurts something else?  Or at least fix the
out of memory error, even if it doesn't display all the luns?

jeremy

  reply	other threads:[~2005-04-08  7:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-07  9:46 [PATCH] Use proper seq_file api for /proc/scsi/scsi Hannes Reinecke
2005-04-07 10:31 ` Christoph Hellwig
2005-04-07 11:21   ` Hannes Reinecke
2005-04-07 11:24     ` Christoph Hellwig
2005-04-08  7:23       ` Jeremy Higdon [this message]
2005-04-08  7:56         ` Christoph Hellwig
2005-04-08  7:59           ` Arjan van de Ven
2005-04-08  8:10           ` Jeremy Higdon
2005-04-08 14:27             ` 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=20050408072345.GA1018765@sgi.com \
    --to=jeremy@sgi.com \
    --cc=hare@suse.de \
    --cc=hch@infradead.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