Kernel moving to Linux v5.14

[Tao Ren]

On Wed, Sep 22, 2021 at 06:11:18AM +0000, Joel Stanley wrote:
> On Wed, 22 Sept 2021 at 06:08, Tao Ren <rentao.bupt at gmail.com> wrote:
> >
> > On Wed, Sep 22, 2021 at 12:24:46AM +0000, Joel Stanley wrote:
> > > On Tue, 14 Sept 2021 at 02:11, Joel Stanley <joel at jms.id.au> wrote:
> > > >
> > > > The openbmc kernel will move to a 5.14 based tree for Aspeed and
> > > > Nuvoton machines.
> > > >
> > > >     linux-openbmc: Move to Linux v5.14
> > > >
> > > >     This moves the OpeNBMC kernel to a v5.14 base. There are 78 patches in
> > > >     the tree, plus a the MCTP core and device tree changes that were merged
> > > >     in v5.15 which have been backported.
> > > >
> > > > https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/46847
> > >
> > > This has now been merged. Thank you to those who reviewed the change.
> > >
> > > Please address future kernel changes to the dev-5.14 tree.
> > >
> > > Cheers,
> > >
> > > Joel
> >
> > Thanks Joel for carrying and backporting the patches. I'm also porting
> > Linux v5.14 to Facebook OpenBMC tree and these patches are very helpful.
> 
> Thanks, I appreciate you saying so.
> 
> Even more helpful would be to have your patches in the openbmc tree, I
> would think.
> 
> Would you consider doing that, instead of us both having to spend time
> maintaining separate trees?
> 
> Cheers,
> 
> Joel

Hi Joel,

I'd love to share the same kernel tree, but I'm afraid it will introduce
a lot of overhead for you at this stage, because we still have a set of
local patches which may take a while to upstream (mainly due to resource
constraints).

In other word, sharing the same kernel tree is my goal, but we are not
fully ready yet (couldn't meet three iterations policy) :)


Cheers,

Tao