From: Roman Zippel <zippel@linux-m68k.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: struct inode size reduction.
Date: Mon, 10 Mar 2003 17:25:49 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0303101620020.5042-100000@serv> (raw)
In-Reply-To: <20030310120534.GA4125@win.tue.nl>
Hi,
On Mon, 10 Mar 2003, Andries Brouwer wrote:
> > > - error = register_chrdev(driver->major, driver->name, &tty_fops);
> > > + error = register_chrdev_region(driver->major, driver->minor_start,
> > > + driver->num, driver->name, &tty_fops);
> >
> > Are that much parameters really needed?
>
> Yes.
Why? Problems are hardly solved by adding more parameters.
If going to a larger number space means, that we have to add crappy
interfaces, we should rather keep it as it is.
Why do you need to partition the number space like this? I looked at the
users in the last mail for a reason. If we're going to change the
interface, it should reflect what we will need in the future.
bye, Roman
next prev parent reply other threads:[~2003-03-10 16:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 13:54 Dave Jones
2003-03-09 17:13 ` Andries Brouwer
2003-03-09 20:33 ` Dave Jones
2003-03-09 19:55 ` Christoph Hellwig
2003-03-09 20:31 ` Andries Brouwer
2003-03-09 22:18 ` Roman Zippel
2003-03-09 23:08 ` Andries Brouwer
2003-03-10 2:23 ` Alexander Viro
2003-03-10 10:58 ` Roman Zippel
2003-03-10 12:05 ` Andries Brouwer
2003-03-10 16:25 ` Roman Zippel [this message]
2003-03-10 17:32 ` Andries Brouwer
2003-03-10 18:39 ` Roman Zippel
2003-03-09 22:45 ` J.A. Magallon
2003-03-10 0:11 ` Dave Jones
2003-03-09 23:59 ` J.A. Magallon
2003-03-10 5:04 ` Miles Bader
2003-03-10 9:30 Fwd: " Andries.Brouwer
2003-03-10 9:32 Andries.Brouwer
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.0303101620020.5042-100000@serv \
--to=zippel@linux-m68k.org \
--cc=aebr@win.tue.nl \
--cc=davej@codemonkey.org.uk \
--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
all inboxes | Powered by JetHome®