From: Jiri Kosina <jkosina@suse.cz>
To: Roland Dreier <rdreier@cisco.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
LKML <linux-kernel@vger.kernel.org>,
Amanda McPherson <amanda@amcpherson.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH, RFC] A development process document
Date: Wed, 30 Jul 2008 23:38:42 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.1.10.0807302334430.3768@jikos.suse.cz> (raw)
In-Reply-To: <ada3alrys8d.fsf@cisco.com>
On Wed, 30 Jul 2008, Roland Dreier wrote:
> I think Linus has said pretty explicitly that he is willing to merge new
> low-level hardware drivers at pretty much any stage, as long as they are
> obviously self-contained and can't break anything.
Well, I think I understand a little bit this fear of merging new driver
that "obviously can't break anything" in arbitrary stage od development.
See below.
> As an example of this, the UVC webcam driver was one of the very last
> things merged just before the final 2.6.26 release, very late in the
> release cycle.
If you have a hardware that hasn't been supported by the previous kernel
versions at all, then everything is fine, just no driver is bound to the
device, and the device doesn't work. If then -rc9 comes with a shiny new
driver for this hardware, it gets autoloaded. If it is buggy, your system
crashes. This is regression, right?
Nevertheless, I still think that merging new drivers as fast as possible
is a good thing (tm).
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2008-07-30 21:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 20:30 Jonathan Corbet
2008-07-30 7:15 ` Andrew Morton
2008-07-30 18:05 ` Jonathan Corbet
2008-07-30 11:09 ` Jiri Kosina
2008-07-30 16:05 ` Takashi Iwai
2008-07-30 20:56 ` Jonathan Corbet
2008-07-30 21:30 ` Roland Dreier
2008-07-30 21:38 ` Jiri Kosina [this message]
2008-07-31 6:23 ` Alex Chiang
2008-07-31 16:17 ` Jonathan Corbet
2008-07-31 17:49 ` Daniel Barkalow
2008-07-31 17:57 ` Randy.Dunlap
2008-08-01 10:35 ` Stefan Richter
2008-08-01 16:52 ` Daniel Barkalow
2008-07-31 12:22 ` Jochen Voß
2008-07-31 16:30 ` Jonathan Corbet
2008-07-31 23:45 ` Jake Edge
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=alpine.LNX.1.10.0807302334430.3768@jikos.suse.cz \
--to=jkosina@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=amanda@amcpherson.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
/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®