From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: benh@kernel.crashing.org,
ksummit-2008-discuss@lists.linux-foundation.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-2008-discuss] Request for discussion on when to merge drivers
Date: Thu, 19 Jun 2008 11:13:37 +0200 [thread overview]
Message-ID: <485A2341.9020406@s5r6.in-berlin.de> (raw)
In-Reply-To: <1213832399.3515.109.camel@localhost.localdomain>
James Bottomley wrote:
> On Thu, 2008-06-19 at 09:31 +1000, Benjamin Herrenschmidt wrote:
>> linux-next should, imho, exclusively be for things we are pretty much
>> commited to merge in the next release. ie, a staging place to fixup
>> things like build breakages, patch conflicts, etc...
>>
>> Or else, it will just be another -mm ....
>
> Well, as Greg said for his driver staging tree, I think we can elide
> this requirement for new drivers. The good thing about drivers is that
> there's nothing we're really doing to break anything: before the driver
> the hardware was just plane unusable with Linux after the driver well,
> we're hoping it might be ...
This requires that the staged driver does not contain build bugs on any
architecture.
Besides, the definition of what we published in -next so far was:
Everything in -next is *merge-ready* now (from a subsystem
maintainer's POV). The only reason that it is not merged yet
is that Linus doesn't have a merge window open right now.
And the goal of -next was to check for potential integration problems
that cannot be detected in a maintainer's tree.
So IMO the question is not whether to put stuff which is not ready to be
merged into -next. It shouldn't, IMO. The questions rather are:
- What are criteria for merge-readiness of drivers?
(When do we have to / are we able to address issues like CamelCase
names or use of obsolete APIs --- before or after merge?)
- How to publish drivers which are not yet merge-ready but should get
into the hands of testers?
IMO the answer to the latter question is still not -next, because the
testing that -next gets is (from what I understood) also with the
specific goal to detect potential integration problems. Remember, you
publish code in -next of which you can say: This is ready for mainline,
except that there is little experience yet WRT potential integration issues.
--
Stefan Richter
-=====-==--- -==- =--==
http://arcgraph.de/sr/
prev parent reply other threads:[~2008-06-19 9:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 15:27 James Bottomley
2008-06-18 17:15 ` [Ksummit-2008-discuss] " Luck, Tony
2008-06-18 17:34 ` James Bottomley
2008-06-18 17:30 ` Benny Halevy
2008-06-18 23:20 ` [Ksummit-2008-discuss] " Jiri Kosina
2008-06-19 7:34 ` Benny Halevy
2008-06-18 18:38 ` Mauro Carvalho Chehab
2008-06-18 23:31 ` Benjamin Herrenschmidt
2008-06-18 23:39 ` [Ksummit-2008-discuss] " James Bottomley
2008-06-18 23:48 ` Jiri Kosina
2008-06-19 9:13 ` Stefan Richter [this message]
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=485A2341.9020406@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=benh@kernel.crashing.org \
--cc=ksummit-2008-discuss@lists.linux-foundation.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®