From: Christoph Hellwig <hch@infradead.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Greg KH <greg@kroah.com>,
Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
akpm@digeo.com
Subject: Re: [PATCH] alternative dev patch
Date: Sun, 23 Mar 2003 16:32:23 +0000 [thread overview]
Message-ID: <20030323163223.A9499@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303231557230.5042-100000@serv>; from zippel@linux-m68k.org on Sun, Mar 23, 2003 at 04:05:24PM +0100
On Sun, Mar 23, 2003 at 04:05:24PM +0100, Roman Zippel wrote:
> > Yeah, but as I know, it's a big pain in the butt. Let's make it easy to
> > do this, don't make writing a driver tougher than it has to be (it's
> > already much harder than it used to be.) Andries's patch makes it easy,
> > which is a good thing in my book.
>
> Andries' patch doesn't help at all and only makes things worse. Only very
> few drivers should have to deal with the major/minor business. Most
> drivers should just do add_serial_device/add_tape_device/... and these
> function will do the right thing (e.g. announce the new device via sysfs).
Yupp. The add_serial_device/add_tape_device/ would also have the benefit
that they could keept track of devfs like the gendisk handling when
GENHD_FL_DEVFS is set by the drivers - lots of cruft can be remove from
drivers and midlayers incrementally.
next prev parent reply other threads:[~2003-03-23 16:21 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 [this message]
2003-03-23 8:50 ` Christoph Hellwig
2003-03-23 8:46 ` Christoph Hellwig
2003-03-23 15:11 ` Roman Zippel
-- 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=20030323163223.A9499@infradead.org \
--to=hch@infradead.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.