Ameya Palande had written, on 10/18/2010 10:43 AM, the following:
Hi Nishanth,

On Sat, 2010-10-16 at 02:20 +0200, ext Nishanth Menon wrote:
To ease things, I back ported the patches and hosted them here:
github: http://github.com/nmenon/linux-meego-panda
Git: git://github.com/nmenon/linux-meego-panda.git
http: https://[email protected]/nmenon/linux-meego-panda.git

Branches
master inline with linus tree as of today

base-v2.6.36-rc4 (2.6.36-rc4 base - same as kernel-dev)
|
|
`-----omap-for-linus-import (patches from linux-omap's for_next which   
        |                       imported straight to 2.6.34-rc4)
        |
        `---- omap-for-linus-backport (additional omap-for-linus patches
                |       I had to fix up for 2.6.34 - i have added the
                |       orignal links here as well)
                |
                `---- additional-rebases (extra patches from .36-rc4 to
                                .36-rc8 that I pulled in from ARM
                                changes + 1 patch from mfd tree for
                                mmc omap4 hotplug + 1 patch i posted in
                                linux-omap - all with links)

I guess I'd have to post out the omap-for-linus-backport for review in meego-ml -> I dont have an issue if we are ok to go ahead in this path..

Once kernel-dev in meego moves to 36-rc8 things will be simpler :)
Assuming kernel-dev moves to 36-rc8 soon, I can see following steps to
get panda board support in meego:

1. Patches which should end up in 37-rc1 = omap-for-linus-import +
omap-for-linus-backport + some chunk of additional-rebases.

Since these will be accepted for 37-rc1 there is no need to post them
again to meego-kernel mailing list. You can link devel:kernel kernel-dev
in your project and stack these patches on top of it and send a request
(using "osc submitrequest").

2. Remaining patches (1 patch from mfd tree etc.) should be posted to
meego kernel mailing list with reference link to discussions/review
being done at linux-omap mailing list. Once they are accepted you can
create another submitrequest and get them in kernel-dev package.

Let me know if you need more information :)
This sounds like a plan. I already see you have asked Alan about this[1] - will send out submit once we move to rc8.

[1]http://lists.meego.com/pipermail/meego-kernel/2010-October/000607.html
--
Regards,
Nishanth Menon
_______________________________________________
Meego-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel

Reply via email to