From: Roman Zippel <zippel@linux-m68k.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andries.Brouwer@cwi.nl, <linux-kernel@vger.kernel.org>, <akpm@digeo.com>
Subject: Re: [PATCH] alternative dev patch
Date: Sun, 23 Mar 2003 16:11:16 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0303231605470.5042-100000@serv> (raw)
In-Reply-To: <20030323084621.A6788@infradead.org>
Hi,
On Sun, 23 Mar 2003, Christoph Hellwig wrote:
> That;s not exactly true. A tradition major device is nothing but a
> region with a fixed size, and we need to get rid of this major/minor
> thinking. Converting a dev_t to struct char_device * / struct block_device *
> early is the way we wan't to go for that. It helped the block layer
> a lot..
I basically agree, I only want to note that the block layer only has to
deal with disks, where we have different types of character devices. So
having one major per serial/tape/tty/... devices might not be necessary,
but it could makes things bit easier. In any case the actual drivers
should not see any of this.
bye, Roman
next prev parent reply other threads:[~2003-03-23 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 21:50 [PATCH] alternative dev patch Andries.Brouwer
2003-03-20 23:03 ` Roman Zippel
2003-03-21 1:24 ` Greg KH
2003-03-21 9:08 ` Roman Zippel
2003-03-22 1:38 ` Greg KH
2003-03-22 13:02 ` Roman Zippel
2003-03-23 8:19 ` Greg KH
2003-03-23 8:30 ` Christoph Hellwig
2003-03-23 15:05 ` Roman Zippel
2003-03-23 16:32 ` Christoph Hellwig
2003-03-23 8:50 ` Christoph Hellwig
2003-03-23 8:46 ` Christoph Hellwig
2003-03-23 15:11 ` Roman Zippel [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-20 0:57 Roman Zippel
2003-03-20 20:40 ` Roman Zippel
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=Pine.LNX.4.44.0303231605470.5042-100000@serv \
--to=zippel@linux-m68k.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).