On 2014-12-11 10:29, Russell King - ARM Linux wrote:
On Wed, Dec 10, 2014 at 10:42:33AM +0100, Marek Szyprowski wrote:
I assume that now it won't be possible to get l2c patches back to -next,
so I will resend them (again...) with the omap related fix.
What, you mean you don't know the fundamental rules of kernel development?
No one should ever dump any new code into linux-next during a merge
window which is not a fix for a regression or a bug fix, period.
Linus has in the past taken a snapshot of linux-next at the beginning
of a merge window, and then threatened to refuse to merge anything that
wasn't in his local snapshot, or which doesn't qualify as the above.
So no, it won't be possible, because I play by the community rules when
it comes to what gets merged and at what time in the cycle.
I know the rules. It was just my whining, that it is yet another release
cycle
that got missed. It is really disappointing, that those patches have been
floating for months and noone found issues related to different order of
initialization. It took way to long to get them scheduled for testing in
-next.
Exynos4 platform cannot be considered as fully functional without
proper l2cache support, but I assume that this is once again our fault that
we had to modify the common l2c code.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
