All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>,
	Tao Ren <taoren@fb.com>,
	 OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Moving to Linux Kernel 5.0
Date: Wed, 20 Mar 2019 06:56:59 +0000	[thread overview]
Message-ID: <CACPK8XdkV=n6WRZXQv3OX=F=AVUhy2ULjCT_ceU3eCc9DahOMQ@mail.gmail.com> (raw)
In-Reply-To: <819d0ff4-7ed5-8527-bd92-1ff468f699ed@linux.intel.com>

On Mon, 18 Mar 2019 at 22:29, Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com> wrote:
> > It's been a few releases since we bumped, so I'm going to publish a
> > 5.0 based tree this week. I've done some testing on the machine I have
> > (OpenPower Romulus ast2500) and it looks good.
> >
> > I'll be rebasing without discarding patches for this release. That
> > means if you have non-mainline patches it will still be there for
> > dev-5.0. Next release we will do a cleanout, so please ensure your out
> > of tree patches are on the upstream lists for 5.2 now.
> >
> I see the out of tree PECI patches are still in dev-5.0. Thanks much
> for rebasing it while you make the kernel update. I checked that
> dev-5.0 kernel works well in my machine.
>
> Again, thanks for your effort!

Thanks for the kind words Tao and Jae.

I've done some further testing on Palmetto (ast2400) as well as
Romulus, and with Jae's testing I think it looks good to go. I have
pushed the dev-5.0 branch to openbmc github, and submitted a patch to
Gerrit to move us to this new base:

 https://gerrit.openbmc-project.xyz/c/openbmc/meta-aspeed/+/19335

The 4.19 tree is now closed. Please address future patches to the 5.0 tree.

Cheers,

Joel

  reply	other threads:[~2019-03-20  6:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18  6:16 Moving to Linux Kernel 5.0 Joel Stanley
2019-03-18 17:44 ` Tao Ren
2019-03-18 22:29 ` Jae Hyun Yoo
2019-03-20  6:56   ` Joel Stanley [this message]
2019-03-19  0:02 ` Andrew Jeffery

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='CACPK8XdkV=n6WRZXQv3OX=F=AVUhy2ULjCT_ceU3eCc9DahOMQ@mail.gmail.com' \
    --to=joel@jms.id.au \
    --cc=jae.hyun.yoo@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=taoren@fb.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.