Linux dev-4.19

[David Thompson]

Since 4.19 kernel is deemed "longterm" with a projected EOL of Dec 2020, is the plan to keep OpenBMC on this kernel version for a while?  

I've yet to upstream any of my changes, my bad, and as a 
result I've gone through four kernel upgrades this year
{4.13, 4.17, 4.18, and now 4.19}.

I'm curious about the OpenBMC kernel upgrade strategy,
esp. after 4.19.

Regards,
- Dave

-----Original Message-----
From: openbmc <openbmc-bounces+dthompson=mellanox.com at lists.ozlabs.org> On Behalf Of Joel Stanley
Sent: Monday, December 3, 2018 5:05 PM
To: Amithash Prasad <amithash at fb.com>
Cc: OpenBMC Maillist <openbmc at lists.ozlabs.org>; vijaykhemka at fb.com
Subject: Re: Linux dev-4.19

On Tue, 4 Dec 2018 at 07:25, Amithash Prasad <amithash at fb.com> wrote:
>
> >> I have couple of NCSI patch which were up streamed last week in linux-next kernel. Will those be part of this 4.19 kernel in openbmc or what is procedure to pull those patches in openbmc build. As these are required for Meta-facebook build with networking working.
> Joel,
>
> Thanks for cherry-picking a few of the NCSI changes into dev-4.19! Along with these, can we get a couple more cherry-picked into dev-4.19?
>
> One patch from linux-next:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/co
> mmit/net/ncsi?h=next-20181203&id=16e8c4ca21a238cdf0355475bf15bd72e92fe
> b8f
>
> One merged patch to bring in the Tiogapass device tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commi
> t/arch/arm/boot/dts/aspeed-bmc-facebook-tiogapass.dts?id=3368e06e2a91a
> 65cff59e520acc51b9adf4900bf

Nice work. This is a great way to request the patches get merged. I'm happy because they're already on their way upstream, and the URLs with SHAs make it easy for me to cherry pick.

Merged!

Cheers,

Joel