From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Norberto Bensa <norberto+linux-kernel@bensa.ath.cx>,
linux-kernel@vger.kernel.org
Subject: Re: does udev support sw raid0?
Date: Fri, 14 May 2004 19:51:21 +0100 [thread overview]
Message-ID: <20040514195121.A27504@infradead.org> (raw)
In-Reply-To: <20040514184659.GA2401@kroah.com>; from greg@kroah.com on Fri, May 14, 2004 at 11:46:59AM -0700
On Fri, May 14, 2004 at 11:46:59AM -0700, Greg KH wrote:
> How did this work with devfs then? The device node would not be present
> before the ioctl needed to be called, right? Or did it do the "magic
> lookup" mess and just "know" about md devices?
md uses blk_register_region to get a callback for it's dev_t region without
a registered gendisk, and also creates devfs entries before the gendisk
is registered. It's a single big mess.
next prev parent reply other threads:[~2004-05-14 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 17:42 does udev support sw raid0? Norberto Bensa
2004-05-14 18:34 ` Greg KH
2004-05-14 18:39 ` Christoph Hellwig
2004-05-14 18:46 ` Greg KH
2004-05-14 18:51 ` Christoph Hellwig [this message]
2004-05-14 19:10 ` Kevin P. Fleming
2004-05-14 18:50 ` Norberto Bensa
2004-05-14 18:48 ` Norberto Bensa
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=20040514195121.A27504@infradead.org \
--to=hch@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=norberto+linux-kernel@bensa.ath.cx \
/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