From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@digeo.com>,
Andries.Brouwer@cwi.nl,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] register_blkdev
Date: Sat, 8 Mar 2003 19:50:28 +0000 [thread overview]
Message-ID: <20030308195028.A31394@infradead.org> (raw)
In-Reply-To: <20030308193722.GD26374@kroah.com>; from greg@kroah.com on Sat, Mar 08, 2003 at 11:37:22AM -0800
On Sat, Mar 08, 2003 at 11:37:22AM -0800, Greg KH wrote:
> That's a good start, but why not change that to a simple,
> HOW_MANY_MINORS_I_WANT, which will work the same way now, but allow us
> to change to a pure dynamic major/minor allocation scheme in the future
> by only modifying the register_chr_device() code. Same thing for
> register_blkdev().
register_blkdev() _IS_ totally meaningless in 2.5. I said this about three
times in this thread already, when will people actually take a look at
the code they look at?
next prev parent reply other threads:[~2003-03-08 19:41 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 19:32 [PATCH] register_blkdev Andries.Brouwer
2003-03-07 19:36 ` Christoph Hellwig
2003-03-07 20:30 ` Andrew Morton
2003-03-07 22:12 ` Greg KH
2003-03-07 22:33 ` Andrew Morton
2003-03-07 23:45 ` Greg KH
2003-03-08 1:14 ` Alan Cox
2003-03-08 0:50 ` Greg KH
2003-03-08 1:05 ` Andrew Morton
2003-03-08 1:03 ` Greg KH
2003-03-08 1:13 ` Linus Torvalds
2003-03-08 15:09 ` Alan Cox
2003-03-08 15:53 ` Christoph Hellwig
2003-03-09 2:02 ` Chris Wedgwood
2003-03-10 4:46 ` Oliver Xymoron
2003-03-08 15:11 ` Alan Cox
2003-03-08 19:37 ` Greg KH
2003-03-08 19:50 ` Christoph Hellwig [this message]
2003-03-08 20:00 ` Greg KH
2003-03-08 20:23 ` Christoph Hellwig
2003-03-07 22:55 ` Joel Becker
2003-03-07 22:57 ` Christoph Hellwig
2003-03-07 23:17 ` Randy.Dunlap
2003-03-07 23:38 ` John Cherry
2003-03-07 23:36 ` Christoph Hellwig
2003-03-07 23:46 ` Andrew Morton
2003-03-07 23:54 ` Christoph Hellwig
2003-03-08 1:49 ` Joel Becker
2003-03-08 1:58 ` Greg KH
2003-03-08 2:15 ` Joel Becker
2003-03-08 2:18 ` Linus Torvalds
2003-03-08 2:42 ` Joel Becker
2003-03-08 19:31 ` Greg KH
2003-03-08 21:39 ` Joel Becker
2003-03-08 21:59 ` Greg KH
2003-03-08 1:04 ` Alan Cox
2003-03-09 4:32 ` Horst von Brand
2003-03-09 5:11 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2003-03-08 20:59 Andries.Brouwer
2003-03-08 21:09 ` Christoph Hellwig
2003-03-08 20:26 Andries.Brouwer
2003-03-08 20:31 ` Christoph Hellwig
2003-03-08 1:49 Andries.Brouwer
2003-03-08 0:57 Andries.Brouwer
2003-03-08 0:53 ` Greg KH
[not found] ` <20030308073407.A24272@infradead.org>
2003-03-08 19:29 ` Greg KH
2003-03-08 19:43 ` Christoph Hellwig
2003-03-08 21:26 ` H. Peter Anvin
2003-03-08 21:55 ` Christoph Hellwig
2003-03-08 21:41 ` Joel Becker
2003-03-08 21:52 ` Christoph Hellwig
2003-03-08 22:16 ` Joel Becker
2003-03-08 22:21 ` Christoph Hellwig
2003-03-10 17:31 ` Joel Becker
2003-03-08 23:37 ` Alan Cox
2003-03-08 22:36 ` Linus Torvalds
2003-03-08 23:56 ` Alan Cox
2003-03-09 5:08 ` Gerrit Huizenga
2003-03-17 19:21 ` Steven Dake
2003-03-07 19:50 Andries.Brouwer
2003-03-07 19:52 ` Christoph Hellwig
2003-03-07 18:49 Andries.Brouwer
2003-03-07 19:06 ` Christoph Hellwig
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=20030308195028.A31394@infradead.org \
--to=hch@infradead.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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).