From: David Weinehall <tao@debian.org>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org, mochel@digitalimplant.org,
axboe@suse.de
Subject: Re: /sys/block vs. /sys/class/block
Date: Thu, 23 Dec 2004 07:39:38 +0100 [thread overview]
Message-ID: <20041223063938.GA27718@khan.acc.umu.se> (raw)
In-Reply-To: <20041222062057.GC31513@kroah.com>
On Tue, Dec 21, 2004 at 10:20:57PM -0800, Greg KH wrote:
[snip]
> It is gross.
Indeed.
> But I guess I should ask, who really cares about this, so late in the
> sysfs structure game? Is /sys/block/ really a big problem for anyone?
> And if it is, I'd much rather someone make the required driver core
> changes to fix this up properly, than just put a symlink to paper over
> some userspace issue.
Maybe because *for once* it'd be nice to actually have inconsistencies
gotten rid of in their relative infancy instead of waiting 10 years
and then having to explain them as existing only for hysterical
raisins...
[snip]
Regards: David Weinehall
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2004-12-23 6:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 7:08 Benjamin Herrenschmidt
2004-12-20 8:16 ` Nick Piggin
2004-12-20 9:29 ` Benjamin Herrenschmidt
2004-12-20 9:44 ` Nick Piggin
2004-12-20 9:45 ` Jens Axboe
2004-12-20 11:37 ` Jan Engelhardt
2004-12-20 14:08 ` Jens Axboe
2004-12-20 22:49 ` Greg KH
2004-12-21 7:07 ` Benjamin Herrenschmidt
2004-12-22 2:34 ` Daniel Stekloff
2004-12-22 4:34 ` Stephen Rothwell
2004-12-22 6:20 ` Greg KH
2004-12-23 6:39 ` David Weinehall [this message]
2004-12-23 6:55 ` Benjamin Herrenschmidt
2005-01-06 23:14 ` 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=20041223063938.GA27718@khan.acc.umu.se \
--to=tao@debian.org \
--cc=axboe@suse.de \
--cc=benh@kernel.crashing.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=sfr@canb.auug.org.au \
/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®