[Ksummit-2012-discuss] [ATTEND] Process issues, device model, stable
rostedt at goodmis.org
Tue Jun 19 18:43:31 UTC 2012
On Tue, 2012-06-19 at 19:23 +0100, Mark Brown wrote:
> On Tue, Jun 19, 2012 at 02:12:01PM -0400, Steven Rostedt wrote:
> > Ideally, development should go into the linux-devel, and anything that
> > goes into linux-next from linux-devel should wait a full release cycle
> > before going to Linus's tree.
> That's a six month turnaround time on getting things into mainline -
> that seems way too long for embedded stuff, we're talking 12 month
> product lifecycles here... We possibly want to do things differently
> for core kernel and driver stuff, but the frameworks do have different
> stability requirements here.
Well, code for new or unique devices is a different matter. Code that
does not have an affect on anything else could be the exception to the
Now if you are modifying core code, and perhaps just core ARM code, do
you really want to rush it out, and risk breaking all ARM devices?
Basically, the more the code affects, the more it should be vetted
before getting in. I have no problem with drivers for new devices
skipping linux-next totally. As long as I do not own such device ;-)
More information about the Ksummit-2012-discuss