On Tue, May 5, 2020 at 10:43 PM Xu, Yanfei wrote:
>
> No, you didn't miss any things. I just know that the patches are
> generated from your scripts. And I will resend the patch against
> linux-yocto.
>
ok!
Thanks for the follow up.
It is ok to send things this way if required .. I just was
On Mon, May 4, 2020 at 7:19 PM Paul Gortmaker
wrote:
>
> Bruce, Yocto kernel folks:
>
> Here is the next 5.2.x stable update "extension" primarily created for
> the Yocto project, as the next v5.2.x post-EOL release.
>
> The content is from an audit of what went into the v5.4.19 to v5.4.21
>
No, you didn't miss any things. I just know that the patches are
generated from your scripts. And I will resend the patch against
linux-yocto.
Yanfei
On 5/2/20 11:19 PM, Bruce Ashfield wrote:
Did I miss applying this to the kernel-cache previously ? or did
I miss a patch against the
In message: [PATCH] rt: merge fixup for v5.4.37 and printk issues
on 05/05/2020 Paul Gortmaker wrote:
> In v5.4.37, upstream ab6f762f0f5 ("printk: queue wake_up_klogd
> irq_work only if per-CPU areas are ready") was backported.
>
> However, in preempt-rt content we have:
>
>
In v5.4.37, upstream ab6f762f0f5 ("printk: queue wake_up_klogd
irq_work only if per-CPU areas are ready") was backported.
However, in preempt-rt content we have:
0011-printk_safe-remove-printk-safe-code.patch
0025-printk-remove-unused-code.patch
The v5.6-rt already has a backport of
