From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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: Mon, 20 Dec 2004 19:16:45 +1100 [thread overview]
Message-ID: <41C68A6D.6060801@yahoo.com.au> (raw)
In-Reply-To: <1103526532.5320.33.camel@gaston>
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.
>
> I also didn't find where /sys/block is created, but that's maybe because
> I didn't search too hard :) So I'm not coming up with a patch yet, but
> unless somebody can convince me it should stay here, I'll do so soon.
>
> If the reason not to fix it is backward compatibility, then that would
> really be a shame we managed already to turn the brand new sysfs into a
> mess with no hope of fixing it... If there is really a problem there,
> maybe we could move it and keep a compat symlink for a few kernel
> revs... ?
>
Seems like that's where it belongs.
The reason why it is in /sys/block is because it is apparently a "subsystem",
and using decl_subsys - drivers/block/genhd.c
Nick
next prev parent reply other threads:[~2004-12-20 8:25 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 [this message]
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
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=41C68A6D.6060801@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=axboe@suse.de \
--cc=benh@kernel.crashing.org \
--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
Powered by JetHome