All of lore.kernel.org
 help / color / mirror / Atom feed
* Moving to Linux Kernel 5.0
@ 2019-03-18  6:16 Joel Stanley
  2019-03-18 17:44 ` Tao Ren
                   ` (2 more replies)
  0 siblings, 3 replies; 5+ messages in thread
From: Joel Stanley @ 2019-03-18  6:16 UTC (permalink / raw)
  To: OpenBMC Maillist

Hello,

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.

Cheers,

Joel

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Moving to Linux Kernel 5.0
  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-19  0:02 ` Andrew Jeffery
  2 siblings, 0 replies; 5+ messages in thread
From: Tao Ren @ 2019-03-18 17:44 UTC (permalink / raw)
  To: Joel Stanley, OpenBMC Maillist

Great. Thank you Joel for the update.

Cheers,

- Tao

On 3/17/19, 11:17 PM, "openbmc on behalf of Joel Stanley" <openbmc-bounces+taoren=fb.com@lists.ozlabs.org on behalf of joel@jms.id.au> wrote:

    Hello,
    
    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.
    
    Cheers,
    
    Joel
    


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Moving to Linux Kernel 5.0
  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
  2019-03-19  0:02 ` Andrew Jeffery
  2 siblings, 1 reply; 5+ messages in thread
From: Jae Hyun Yoo @ 2019-03-18 22:29 UTC (permalink / raw)
  To: Joel Stanley, OpenBMC Maillist

On 3/17/2019 11:16 PM, Joel Stanley wrote:
> Hello,
> 
> 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.
> 
> Cheers,
> 
> Joel
> 

Hi Joel,

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!

Cheers,
Jae

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Moving to Linux Kernel 5.0
  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-19  0:02 ` Andrew Jeffery
  2 siblings, 0 replies; 5+ messages in thread
From: Andrew Jeffery @ 2019-03-19  0:02 UTC (permalink / raw)
  To: Joel Stanley, OpenBMC Maillist



On Mon, 18 Mar 2019, at 16:47, Joel Stanley wrote:
> Hello,
> 
> 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.

Hmm, guess I've got some work to do.

> 
> Cheers,
> 
> Joel
>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Moving to Linux Kernel 5.0
  2019-03-18 22:29 ` Jae Hyun Yoo
@ 2019-03-20  6:56   ` Joel Stanley
  0 siblings, 0 replies; 5+ messages in thread
From: Joel Stanley @ 2019-03-20  6:56 UTC (permalink / raw)
  To: Jae Hyun Yoo, Tao Ren, OpenBMC Maillist

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2019-03-20  6:57 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2019-03-19  0:02 ` Andrew Jeffery

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.