From: Pavel Machek <pavel@ucw.cz>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Andries.Brouwer@cwi.nl, Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kdevt-diff
Date: Wed, 23 Apr 2003 17:19:20 +0200 [thread overview]
Message-ID: <20030423151919.GA3035@elf.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0304151445150.5042-100000@serv>
Hi!
> > > Linus, if you still want to go for a single block device major, this patch
> > > is bad idea (at least in this form).
> >
> > I disagree.
>
> Ok, here is a compromise proposal. I don't care very much about the MKDEV
> macro and almost nobody else should care about it either.
> My main concern with a larger dev_t is that people start to go wild and
> waste the number range with crap. So what I'd like to see is some usage
> policy, e.g. nobody should assume a certain dev_t size, so that it's still
> possible to scale it down. If the user has only a small number of devices,
> they should be addressable even with a 16 bit dev_t.
What's the point? Its not like 8 bytes are that much... Your "number
range" is essentially free, and its okay to waste it...
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-04-23 15:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-13 22:45 [PATCH] kdevt-diff Andries.Brouwer
2003-04-14 17:51 ` Joel Becker
2003-04-14 18:00 ` Linus Torvalds
2003-04-14 19:15 ` Joel Becker
2003-04-14 19:34 ` Roman Zippel
2003-04-16 16:43 ` H. Peter Anvin
2003-04-14 18:12 ` Roman Zippel
2003-04-14 18:18 ` Linus Torvalds
2003-04-14 18:31 ` Roman Zippel
2003-04-14 18:40 ` Linus Torvalds
2003-04-14 19:28 ` Roman Zippel
2003-04-14 19:51 ` Linus Torvalds
2003-04-14 20:02 ` Roman Zippel
2003-04-15 13:37 ` Roman Zippel
2003-04-23 15:19 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 22:01 Andries.Brouwer
2003-04-14 22:11 ` Joel Becker
2003-04-14 22:18 ` Valdis.Kletnieks
2003-04-14 22:28 ` Joel Becker
2003-04-16 16:48 ` H. Peter Anvin
2003-04-16 20:19 ` Andries Brouwer
2003-04-16 20:27 ` H. Peter Anvin
2003-04-15 14:04 Andries.Brouwer
2003-04-15 14:53 ` 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=20030423151919.GA3035@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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