From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@digitalimplant.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: /sys/block vs. /sys/class/block
Date: Tue, 21 Dec 2004 08:07:50 +0100 [thread overview]
Message-ID: <1103612870.21771.22.camel@gaston> (raw)
In-Reply-To: <20041220224950.GA21317@kroah.com>
On Mon, 2004-12-20 at 14:49 -0800, Greg KH wrote:
> On Mon, Dec 20, 2004 at 08:08:52AM +0100, Benjamin Herrenschmidt wrote:
> > I'm trying to understand why we have /sys/block instead
> > of /sys/class/block, and so far, I haven't found a single good argument
> > justifying it... It just messes up the so far logical layout of sysfs
> > for no apparent reason.
>
> Because /sys/block happened before /sys/class did. Al Viro converted
> the block layer before I got the struct class stuff working properly
> during 2.5.
>
> And yes, I would like to convert the block layer to use the class stuff,
> but for right now, I can't as class devices don't allow
> sub-classes-devices, and getting to that work is _way_ down on my list
> of things to do.
but can't we at least artificially move it down to /sys/class anyway for
the sake of a sane userland API ?
Ben.
next prev parent reply other threads:[~2004-12-21 7:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 7:08 /sys/block vs. /sys/class/block 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 [this message]
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
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=1103612870.21771.22.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=axboe@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.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