On Fri, Mar 14, 2014 at 7:33 PM, Alexander Holler [off-list ref] wrote:
Am 14.03.2014 14:54, schrieb Linus Walleij:
quoted
On Fri, Mar 14, 2014 at 1:38 PM, Alexander Holler [off-list ref]
wrote:
quoted
quoted
In that case it is hardly a fix that we need to rush out to the entire
world.
And I thought the reason for -rc is actually to fix bugs. But I never
understood the magical ways and timings patches make their way into
mainline. ;)
OK so it works like this: early in the -rc cycle we fix any bugs,
documentation
or whatever. At this point it's *regressions* so the fix need to fix
something
that broke in the merge window (or an earlier merge window).
Sorry, but I don't believe that. It's always time to fix regressions and
bugs.
This thing is not binary. Please consult
Documentation/development-process/2.Process
In this case we are very late in the release cycle, the patch is not
a simple oneliner and I need some more backing proof to know it
is a reasonable fix to push at this time and will not cause new
problems.
So a few Tested-by's from the people using this driver would for
example convince me that it is solving a real problem for them
and it needs to go into fixes.
Yours,
Linus Walleij