From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: ksummit-2008-discuss@lists.linux-foundation.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Request for discussion on when to merge drivers
Date: Thu, 19 Jun 2008 09:31:34 +1000 [thread overview]
Message-ID: <1213831894.8011.29.camel@pasglop> (raw)
In-Reply-To: <1213802866.3515.24.camel@localhost.localdomain>
> The only slight wrinkle (at least for me) is that often the process of
> cleaning up a driver is fairly intensive for a maintainer and turn
> around is a lot faster if you're doing it in a tree you control. (All
> the scsi drivers we've done like this have lived in temporary branches
> while they were being worked on). So perhaps in addition we should be
> encouraging maintainers to run staging branches under similar rules in
> the staging tree, but allowing inclusion into linux-next?
.../...
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 ....
So while what you say makes sense, I think we should only put drivers in
once we have pretty much decided that the drivers in question would be
merged... in which case, why not straight upstream ?
Cheers,
Ben.
next prev parent reply other threads:[~2008-06-18 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 15:27 Request for discussion on when to merge drivers 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 [this message]
2008-06-18 23:39 ` James Bottomley
2008-06-18 23:48 ` Jiri Kosina
2008-06-19 9:13 ` Stefan Richter
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=1213831894.8011.29.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=James.Bottomley@HansenPartnership.com \
--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 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.