watchdog's patches backport from dev to 2.7/warrior
Joel Stanley
joel at jms.id.au
Wed Oct 9 17:56:49 AEDT 2019
On Tue, 8 Oct 2019 at 16:56, Ivan Mikhaylov <i.mikhaylov at yadro.com> wrote:
>
> On Tue, 2019-10-08 at 06:20 +0000, Joel Stanley wrote:
> > On Mon, 7 Oct 2019 at 16:16, Ivan Mikhaylov <i.mikhaylov at yadro.com> wrote:
> > > Hey Joel, Brad,
> > >
> > > Can we backport these patches into 2.7 warrior, please?
> >
> > Sure. There are two ways to achieve this:
> >
> > - apply changes as kernel patches to the kernel in the layer for your
> > machine.
> > - update the kernel to a newer version by updating meta-aspeed
> >
> > As the kernel is not being maintained for the branch, I would suggest
> > updating meta-aspeed is the best way to go.
> Joel, we had same idea about kernel patches for our layer but meta-aspeed
> approach is much better for us. So should I send those patches into gerrit for
> meta-aspeed?
I can handle the updating.
Brad, are we happy with this approach?
We will update the warrior branch to use the same kernel as master.
Cheers,
Joel
> >
> > Cheers,
> >
> > Joel
> >
> > > c536e5f66af75f4301361363e37d7f4e3aa4eb37
> > > ARM: dts: aspeed: vesnin: Add wdt2 with alt-boot option
> > >
> > > 6984ef32d05c2b5567f5d3f09d260ca7cbc2fc27
> > > ARM: dts: aspeed: vesnin: Add secondary SPI flash chip
> > >
> > > 653aedbf02b71d6930959323e76961da98eab858
> > > watchdog: aspeed: add support for dual boot
> > >
> > > Thanks.
> > >
>
More information about the openbmc
mailing list