From: Christoph Hellwig <hch@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@osdl.org>, Linus <torvalds@osdl.org>,
linuxppc64-dev@lists.linuxppc.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PPC64 iSeries viodasd proc file
Date: Fri, 18 Jun 2004 16:17:53 +0100 [thread overview]
Message-ID: <20040618151753.GA21596@infradead.org> (raw)
In-Reply-To: <40D305B4.4030009@pobox.com>
On Fri, Jun 18, 2004 at 11:09:40AM -0400, Jeff Garzik wrote:
> Stephen Rothwell wrote:
> >Hi Andrew,
> >
> >This patch adds a proc file for viodasd so to make it
> >easier to enumerate the available disks. It is in a
> >(somewhat) strange format to try for a simple level of
> >compatability with the old viodasd code (that was in a
> >couple of vendor's kernels).
>
> Exporting redundant information from procfs is a step backwards, since
> we have sysfs.
>
> I would prefer not to apply this. Upstream is for 'getting it right',
> not for dragging every little vendor kernel hack along.
Agreed. And the old viodasd reason was rejected exactly because it was
such a f***ing mess.
next prev parent reply other threads:[~2004-06-18 15:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 6:54 [PATCH] PPC64 iSeries viodasd proc file Stephen Rothwell
2004-06-18 15:09 ` Jeff Garzik
2004-06-18 15:17 ` Christoph Hellwig [this message]
2004-06-20 19:52 ` Jeremy
2004-06-20 21:11 ` Christoph Hellwig
2004-06-21 6:04 ` Greg KH
[not found] ` <cb5afee10406210914451dc6@mail.gmail.com>
2004-06-23 21:15 ` Jeremy Katz
2004-06-23 21:45 ` Jeff Garzik
2004-06-23 22:03 ` Greg KH
2004-06-24 0:38 ` Jeff Garzik
2004-06-24 20:59 ` Greg KH
2004-06-24 21:25 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 23:54 Stephen Rothwell
2004-06-23 23:55 ` Greg KH
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=20040618151753.GA21596@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@osdl.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