All of lore.kernel.org
 help / color / mirror / Atom feed
* watchdog's patches backport from dev to 2.7/warrior
@ 2019-10-07 16:15 Ivan Mikhaylov
  2019-10-08  6:20 ` Joel Stanley
  0 siblings, 1 reply; 5+ messages in thread
From: Ivan Mikhaylov @ 2019-10-07 16:15 UTC (permalink / raw)
  To: openbmc; +Cc: Joel Stanley, Brad Bishop

Hey Joel, Brad,

Can we backport these patches into 2.7 warrior, please?

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.

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

* Re: watchdog's patches backport from dev to 2.7/warrior
  2019-10-07 16:15 watchdog's patches backport from dev to 2.7/warrior Ivan Mikhaylov
@ 2019-10-08  6:20 ` Joel Stanley
  2019-10-08 16:56   ` Ivan Mikhaylov
  0 siblings, 1 reply; 5+ messages in thread
From: Joel Stanley @ 2019-10-08  6:20 UTC (permalink / raw)
  To: Ivan Mikhaylov; +Cc: OpenBMC Maillist, Brad Bishop

On Mon, 7 Oct 2019 at 16:16, Ivan Mikhaylov <i.mikhaylov@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.

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.
>

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

* Re: watchdog's patches backport from dev to 2.7/warrior
  2019-10-08  6:20 ` Joel Stanley
@ 2019-10-08 16:56   ` Ivan Mikhaylov
  2019-10-09  6:56     ` Joel Stanley
  0 siblings, 1 reply; 5+ messages in thread
From: Ivan Mikhaylov @ 2019-10-08 16:56 UTC (permalink / raw)
  To: Joel Stanley; +Cc: OpenBMC Maillist, Brad Bishop

On Tue, 2019-10-08 at 06:20 +0000, Joel Stanley wrote:
> On Mon, 7 Oct 2019 at 16:16, Ivan Mikhaylov <i.mikhaylov@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.
> 
> 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.
> > 

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?

Thanks.

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

* Re: watchdog's patches backport from dev to 2.7/warrior
  2019-10-08 16:56   ` Ivan Mikhaylov
@ 2019-10-09  6:56     ` Joel Stanley
  2019-10-09 12:03       ` Brad Bishop
  0 siblings, 1 reply; 5+ messages in thread
From: Joel Stanley @ 2019-10-09  6:56 UTC (permalink / raw)
  To: Ivan Mikhaylov; +Cc: OpenBMC Maillist, Brad Bishop

On Tue, 8 Oct 2019 at 16:56, Ivan Mikhaylov <i.mikhaylov@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@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.
> > >
>

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

* Re: watchdog's patches backport from dev to 2.7/warrior
  2019-10-09  6:56     ` Joel Stanley
@ 2019-10-09 12:03       ` Brad Bishop
  0 siblings, 0 replies; 5+ messages in thread
From: Brad Bishop @ 2019-10-09 12:03 UTC (permalink / raw)
  To: Joel Stanley; +Cc: Ivan Mikhaylov, OpenBMC Maillist

at 2:56 AM, Joel Stanley <joel@jms.id.au> wrote:

> On Tue, 8 Oct 2019 at 16:56, Ivan Mikhaylov <i.mikhaylov@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@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.

No concerns or issues with this approach from me.

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

end of thread, other threads:[~2019-10-09 12:03 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-07 16:15 watchdog's patches backport from dev to 2.7/warrior Ivan Mikhaylov
2019-10-08  6:20 ` Joel Stanley
2019-10-08 16:56   ` Ivan Mikhaylov
2019-10-09  6:56     ` Joel Stanley
2019-10-09 12:03       ` Brad Bishop

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.