public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
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 10:29:18 +0100	[thread overview]
Message-ID: <1103534958.14050.13.camel@gaston> (raw)
In-Reply-To: <41C68A6D.6060801@yahoo.com.au>


> 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

I'm not convinced ... If you look at how /sys is organized, it really
doesn't make any sense ... block devives are really devices of "class
block", wether we have a block "subsystem" in there is irrelevant imho.

Ben.



  reply	other threads:[~2004-12-20  9:29 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 [this message]
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=1103534958.14050.13.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=nickpiggin@yahoo.com.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