Linux dev-4.19

Joel Stanley joel at
Tue Dec 4 14:19:20 AEDT 2018

Hello Dave,

On Tue, 4 Dec 2018 at 13:43, David Thompson <dthompson at> wrote:
> 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 have no plans to stay on a given release once the next is out at
this stage. My goal is to get all of the code upstream, so that I
don't need to maintain any out of tree patches, and then system
integrator can pick whichever kernel they want for their system.

It would be straight forward to maintain a stable tree once the "dev"
tree has moved on past 4.19. I have some ideas on how this could work
if you are interested.

> 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 encourage you to get your patches on the list! Do you have a run
down of what you keep out of tree?



> I'm curious about the OpenBMC kernel upgrade strategy,
> esp. after 4.19.
> Regards,
> - Dave
> -----Original Message-----
> From: openbmc < at> On Behalf Of Joel Stanley
> Sent: Monday, December 3, 2018 5:05 PM
> To: Amithash Prasad <amithash at>
> Cc: OpenBMC Maillist <openbmc at>; vijaykhemka at
> Subject: Re: Linux dev-4.19
> On Tue, 4 Dec 2018 at 07:25, Amithash Prasad <amithash at> 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:
> >
> > mmit/net/ncsi?h=next-20181203&id=16e8c4ca21a238cdf0355475bf15bd72e92fe
> > b8f
> >
> > One merged patch to bring in the Tiogapass device tree:
> >
> > 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

More information about the openbmc mailing list