From: Christoph Hellwig <hch@lst.de>
To: Chiaki <ishikawa@yk.rim.or.jp>
Cc: Christoph Hellwig <hch@lst.de>,
g.liakhovetski@gmx.de, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] kill tmscsim ->proc_info
Date: Tue, 17 Aug 2004 18:48:24 +0200 [thread overview]
Message-ID: <20040817164824.GA17074@lst.de> (raw)
In-Reply-To: <4122366E.1040204@yk.rim.or.jp>
On Wed, Aug 18, 2004 at 01:46:38AM +0900, Chiaki wrote:
> Christoph Hellwig wrote:
> >hrrible code like all proc_info implementations and no really usefull
> >information. We might want to add sysfs attributes if some users really
> >miss anything.
> >
>
> Setting aside the horribleness of the code and suitability
> of the code for 2.6.x kernel,
> I found the information very useful when I did the debugging
> with tmscsim driver code with
> a rather obscure CD changer device and
> other odd SCSI devices.
What particular information?
next prev parent reply other threads:[~2004-08-17 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 16:18 [PATCH] kill tmscsim ->proc_info Christoph Hellwig
2004-08-17 16:46 ` Chiaki
2004-08-17 16:48 ` Christoph Hellwig [this message]
2004-08-17 17:03 ` Chiaki
2004-08-24 11:31 ` Christoph Hellwig
2004-08-17 20:38 ` Guennadi Liakhovetski
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=20040817164824.GA17074@lst.de \
--to=hch@lst.de \
--cc=g.liakhovetski@gmx.de \
--cc=ishikawa@yk.rim.or.jp \
--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