openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tao Ren <rentao.bupt@gmail.com>
To: Joel Stanley <joel@jms.id.au>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Kernel moving to Linux v5.14
Date: Tue, 21 Sep 2021 23:48:07 -0700	[thread overview]
Message-ID: <20210922064806.GA31719@taoren-ubuntu-R90MNF91> (raw)
In-Reply-To: <CACPK8Xe_fqxMqzRUW1CMa1iJQaOCmVE7fyK7Q2G5zUFHtDGZgA@mail.gmail.com>

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@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@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

      reply	other threads:[~2021-09-22  6:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14  2:11 Kernel moving to Linux v5.14 Joel Stanley
2021-09-22  0:24 ` Joel Stanley
2021-09-22  6:08   ` Tao Ren
2021-09-22  6:11     ` Joel Stanley
2021-09-22  6:48       ` Tao Ren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210922064806.GA31719@taoren-ubuntu-R90MNF91 \
    --to=rentao.bupt@gmail.com \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).