From: Christoph Hellwig <hch@infradead.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 1/3] revert register_chrdev_region change
Date: Mon, 24 Mar 2003 15:04:59 +0000 [thread overview]
Message-ID: <20030324150458.A19789@infradead.org> (raw)
In-Reply-To: <20030324142515.GA10462@win.tue.nl>; from aebr@win.tue.nl on Mon, Mar 24, 2003 at 03:25:15PM +0100
On Mon, Mar 24, 2003 at 03:25:15PM +0100, Andries Brouwer wrote:
> It still looks like you do not understand the purpose of these patches.
> First of all, it is a series - code is morphed into a more desirable
> state; at each point in time there are imperfections, and some of these
> disappear the next stage.
> The first goal is not at all handling many devices. The first goal is
> having a larger dev_t. Handling many devices comes after that.
Well, there's people here who disagree with tour order. And yes, making
dev_t larger before making the kernel ready for a large number of devices
is the wrong way around.
If you look at Roman's patches they don't even hinder your dev_t enlargement
but they provide a singificant benefit. Now I'm personally not yet
completly happy with his interface either because he still uses the
major/minor split, but I'm working on fixing this properly.
next prev parent reply other threads:[~2003-03-24 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 23:25 Roman Zippel
2003-03-24 14:25 ` Andries Brouwer
2003-03-24 14:43 ` Roman Zippel
2003-03-24 15:04 ` Christoph Hellwig [this message]
2003-03-24 16:09 ` Roman Zippel
2003-03-24 19:07 Andries.Brouwer
2003-03-24 19:10 ` Christoph Hellwig
2003-03-24 20:55 ` Roman Zippel
2003-03-24 20:34 Andries.Brouwer
2003-03-24 20:39 ` Christoph Hellwig
2003-03-24 22:06 Andries.Brouwer
2003-03-24 22:28 ` Roman Zippel
2003-03-24 22:40 Andries.Brouwer
2003-03-24 22:52 ` 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=20030324150458.A19789@infradead.org \
--to=hch@infradead.org \
--cc=aebr@win.tue.nl \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®