Ameya Palande had written, on 10/19/2010 10:01 AM, the following:
Hi Arjan,
+ Nishanth Menon (omap4 TI)
thanks. I am part of meego-kernel ML, so no need to explicitly cc me ->
On Tue, 2010-10-19 at 16:52 +0200, ext Arjan van de Ven wrote:
On 10/19/2010 7:50 AM, Ameya Palande wrote:
Hi Alan,
+ Nishanth Menon (omap4 panda board support from Texas Instruments)
On Tue, 2010-10-19 at 15:51 +0200, ext Alan Cox wrote:
I suggest disabling things which break with this move, and fix them
when kernel-dev moves to 2.6.36 release.
It isn't that simple. The rebase will be a big piece of work because of
all the submissions and the stuff that needs dropping out (some of which
in turn of course has dependencies to fix up). In the typical case
stuff flows nicely when you do this but because there has been a lot of
rewriting/fixing it'll take time to square up the driver versions and
make sure nothing gets missed.
Alan
What I am asking is disabling patches (ex.
linux-2.6.36-ac-2010-09-29.patch) in kernel-dev package and upgrade it
to 36-rc8 release.
if you disable that patch the whole package is useless for the x86 mid
platforms.
Yes I understand, and thats why I asked Alan about his plans to upgrade
that patch. Now we have information about that, I see that the only way
we can proceed for 2.6.36-rc8 upgrade is to disable things which are not
in sync.
This was also decided as a strategy for kernel-dev upgrades (that patch
maintainer upgrades his patches to keep them in sync with linux
mainline, or we end up disabling them).
let see where we are:
a) kernel-dev was supposed to stay in sync with bleeding edge kernel as
much as possible -> it is at .36-rc4 and we are at .36-rc8 - almost
like a month behind?
b) what is the point in upstreaming to kernel.org and insistence on it
if we dont force ourselves to rebase?
I am altogether lost as to difference between kernel and kernel-dev if
each of us choose to stick around with the kernel we are all comfortable
with :(
--
Regards,
Nishanth Menon
_______________________________________________
Meego-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
