watchdog's patches backport from dev to 2.7/warrior
Brad Bishop
bradleyb at fuzziesquirrel.com
Wed Oct 9 23:03:14 AEDT 2019
at 2:56 AM, Joel Stanley <joel at jms.id.au> wrote:
> 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.
No concerns or issues with this approach from me.
More information about the openbmc
mailing list