From: Christoph Hellwig <hch@infradead.org>
To: Willem Riede <wrlk@riede.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Updated osst driver for 2.6.x
Date: Sun, 28 Dec 2003 13:25:18 +0000 [thread overview]
Message-ID: <20031228132518.A20134@infradead.org> (raw)
In-Reply-To: <20031223212950.GW1277@linnie.riede.org>; from wrlk@riede.org on Tue, Dec 23, 2003 at 04:29:50PM -0500
On Tue, Dec 23, 2003 at 04:29:50PM -0500, Willem Riede wrote:
> > Please don't. This is exactly what sysfs is for.
> >
> I was afraid you were going to say that :-)
>
> The 2.4 version I have on the osst web site has had this /proc file for some time,
> and I simply copied the logic over.
>
> But if you don't want me to go there, I won't. I'll come back later with a sysfs
> version that provides that info. One question: should each parameter be in its
> own little file, or can I create them all on one line as I do now?
Yes, please do one value per file.
> In the mean time, here is the patch without the offending pieces.
>
> Is this OK? Thanks, Willem Riede.
The patch looks okay to me.
prev parent reply other threads:[~2003-12-28 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 17:43 [PATCH] Updated osst driver for 2.6.x Willem Riede
2003-12-23 19:26 ` Christoph Hellwig
2003-12-23 21:29 ` Willem Riede
2003-12-28 13:25 ` Christoph Hellwig [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=20031228132518.A20134@infradead.org \
--to=hch@infradead.org \
--cc=linux-scsi@vger.kernel.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