From: Jes Sorensen <jes@sgi.com>
To: David Chow <davidchow@shaolinmicro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux drivers management
Date: Mon, 06 Feb 2006 18:42:56 +0100 [thread overview]
Message-ID: <43E78AA0.2090900@sgi.com> (raw)
In-Reply-To: <43E77EEA.7040908@shaolinmicro.com>
David Chow wrote:
>> This is a classic question, by seperating out the drivers you make it
>> so much harder for all developers to propagate changes into all pieces
>> of the tree.
>
> I write drivers, never need to change kernel if the kernel API is mature
> enough to provide the need of a module developer needs. There is no
> reason to make changes to the kernel source, only needed because the
> original kernel code is crap or the API designed without proper
> software/system architectural design work effort. Each Linux kernel
> version go through a lengthy beta release cycle (e.g. 2.3, 2.5, 2.7),
> this shouldn't happen and idea collection should be enough through this
> large Linux community.
Silly me, it was a trick question. I should have known better than to
fall into that trap. See the responses you got from other people already
and go check out the archives.
No even better, here's a link:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/stable_api_nonsense.txt
If you still wish to argue for this, please take me off the CC list.
To be honest, I don't think anyone on linux-kernel is interested in yet
another round of this one.
Cheers,
Jes
next prev parent reply other threads:[~2006-02-06 17:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 9:45 Linux drivers management David Chow
2006-02-06 10:05 ` Michal Schmidt
2006-02-06 16:50 ` David Chow
2006-02-06 16:55 ` Randy.Dunlap
2006-02-06 19:45 ` Alan Cox
2006-02-06 19:46 ` Jesper Juhl
2006-02-06 10:08 ` Jes Sorensen
2006-02-06 16:52 ` David Chow
2006-02-06 17:03 ` Pedro Alves
2006-02-06 17:35 ` Geert Uytterhoeven
2006-02-06 17:42 ` Jes Sorensen [this message]
2006-02-06 16:56 ` Christoph Hellwig
2006-02-07 11:36 ` Denis Vlasenko
2006-02-07 13:22 ` Christoph Hellwig
2006-02-06 19:51 ` Greg KH
2006-02-06 21:38 ` Jim Crilly
-- strict thread matches above, loose matches on Subject: below --
2006-02-06 18:31 Nicolas Mailhot
2006-02-06 18:56 ` Yaroslav Rastrigin
2006-02-06 19:02 ` Joshua Kugler
2006-02-06 19:17 ` Yaroslav Rastrigin
2006-02-06 19:39 ` Martin Mares
2006-02-06 19:56 ` Jan-Benedict Glaw
2006-02-06 19:53 ` Jan-Benedict Glaw
2006-02-06 20:04 ` Jesper Juhl
2006-02-06 23:52 ` Bernd Petrovitsch
2006-02-06 19:21 ` linux-os (Dick Johnson)
2006-02-06 19:46 ` Michael Krufky
2006-02-06 19:58 ` Nicolas Mailhot
2006-02-06 23:16 ` Gene Heskett
2006-02-06 19:30 Nicolas Mailhot
2006-02-07 4:42 linux
2006-02-07 16:18 ` Eric W. Biederman
2006-02-07 19:45 ` David Chow
2006-02-07 20:03 ` Kyle Moffett
2006-02-07 22:15 ` Theodore Ts'o
2006-02-08 0:52 ` David Chow
2006-02-08 4:02 ` Theodore Ts'o
2006-02-08 9:46 ` Bernd Petrovitsch
2006-02-09 6:09 ` Lee Revell
2006-02-08 1:06 ` Alan Cox
2006-02-08 8:26 ` Denis Vlasenko
2006-02-11 18:47 ` Andrew James Wade
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=43E78AA0.2090900@sgi.com \
--to=jes@sgi.com \
--cc=davidchow@shaolinmicro.com \
--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 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.