From: Greg KH <greg@kroah.com>
To: Jeremy <jeremy.katz@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jeff Garzik <jgarzik@pobox.com>,
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: Sun, 20 Jun 2004 23:04:35 -0700 [thread overview]
Message-ID: <20040621060435.GA28384@kroah.com> (raw)
In-Reply-To: <cb5afee1040620125272ab9f06@mail.gmail.com>
On Sun, Jun 20, 2004 at 03:52:33PM -0400, Jeremy wrote:
> > Agreed. And the old viodasd reason was rejected exactly because it was
> > such a f***ing mess.
>
> The argument could be made that sysfs is similarly a f***ing mess and
> that instead of solving problems, it creates more.
It does? Have you brought this up to the sysfs / kobject / driver model
authors? I think they would be open to any critiques of the current
code, especially if such critique contains patches.
> The mess of symlinks present there is a disaster and disgusting for
> anyone who wants to actually write clean probing code.
What do you mean by this. Any examples?
> Also, things in sysfs aren't exactly stable enough to count on as a
> dependable interface, but that's something the kernel has never
> reliably exported to userspace.
Why isn't sysfs stable enough? You can find any driver instantly. And
any device bound to that driver in a stable and repeatable manner.
So, give me specific examples, or stop ranting for no reason.
greg k-h
next prev parent reply other threads:[~2004-06-21 6:06 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
2004-06-20 19:52 ` Jeremy
2004-06-20 21:11 ` Christoph Hellwig
2004-06-21 6:04 ` Greg KH [this message]
[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=20040621060435.GA28384@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jeremy.katz@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.