From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <hch@infradead.org>
Cc: <alan@lxorguk.ukuu.org.uk>, <linux-kernel@vger.kernel.org>,
<torvalds@transmeta.com>
Subject: Re: PATCH: fix proc handling in sis, siimageand slc90e66
Date: Sat, 22 Mar 2003 09:34:27 -0800 (PST) [thread overview]
Message-ID: <33548.4.64.238.61.1048354467.squirrel@www.osdl.org> (raw)
In-Reply-To: <20030322141522.A26332@infradead.org>
> On Sat, Mar 22, 2003 at 03:03:06PM +0000, Alan Cox wrote:
>> On Sat, 2003-03-22 at 07:49, Christoph Hellwig wrote:
>> > > +
>> > > + return len > count ? count : len;
>> >
>> > Shouldn't this just move to the seq_file interface? (probably the
>> "simple" variant)
>>
>> That means making the 2.4 and 2.5 drives diverge which is a pain I don't
>> want before 2.6
>
> The seq_file interface is already and a backport of the single stuff is
> trivial and should happen anyway.
I agree. I helped someone do that for /proc/mdstat[s?] in 2.4
about 2 weeks ago. Very simple to do.
~Randy
prev parent reply other threads:[~2003-03-22 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 19:36 Alan Cox
2003-03-22 7:49 ` Christoph Hellwig
2003-03-22 15:03 ` Alan Cox
2003-03-22 14:15 ` Christoph Hellwig
2003-03-22 17:34 ` Randy.Dunlap [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=33548.4.64.238.61.1048354467.squirrel@www.osdl.org \
--to=rddunlap@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®