[oe] [RFC] How to handle external kernel patches in oe the right way?
papercrane at gmail.com
Wed Sep 5 19:36:14 CEST 2007
On 9/5/07, Nils Faerber <nils.faerber at kernelconcepts.de> wrote:
> Stefan Schmidt schrieb:
> > Hello.
> > Due to my work on OpenEZX (http://www.openezx.org) I'm in touch with
> > external kernel patches used in OE to build working kernels for
> > different Motorola mobile phones.
> > Talking with Koen about the best way to handle this we have some
> > slightly different opinions on this. So we like to get some more
> > opinions on this before pinning to a strategy.
> > Koen like to pull the patches from a known-good rev into oe to have
> > them all at one place for less fragile building and tweaking.
> > I prefer OE to use our svn server with a fixed SRCREV which gets
> > updated once a newer version is known good. I'm not a fan of
> > duplicating the patches in OE if some small tweaking patches can also
> > handle it.
> To add my 0.02€ ;)
> I also see both points, for good and for bad.
> I have the same situation here currently, I am doing the integration of
> a third party board (which will be committed to OE...). The board
> manufacturer does it's own kernel port and maintains own patches. But
> the manufacturer does not do the OE maintenance.
> Including the patch in OE would mean that the patch is stale and once
> the kernel maintainer creates a new patch (against the same kernel
> version) they would have to send the patch to me so that I can get it
> into OE.
> So I decided for now to directly pull the patch from their external
> source. If they do updates they would be automatically included in a
> next build.
That's not really true. OE won't rebuild the kernel unless the PR has
been changed. When they update their patch they still need to tell you
so that you can update the PR in OE.
More information about the Openembedded-devel