mbox series

[0/7] linux-yocto: consolidated pull request

Message ID 20260106152352.932717-1-bruce.ashfield@gmail.com
Headers show
Series linux-yocto: consolidated pull request | expand

Message

Bruce Ashfield Jan. 6, 2026, 3:23 p.m. UTC
From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi all,

I'm still tweaking my pull request scripts for the split repositories,
so apologies if something doesn't look quite right.

I'm unable to push to openembedded-contrib right now, so this is a
patch only send.

We are getting closer to removing 6.16 (and then 6.12) from oe-core
master. These updates should address some config warnings, and
otherwise improve stability.

We need to get the reference platforms update to 6.18, so I've cc'
kevin@windriver to see if he has any plans or comments on that.

Cheers,

Bruce

OE-core (7):
  linux-yocto/6.18: genericarm64: remove SLIM_QCOM_CTR
  linux-yocto/6.12: update to v6.12.63
  linux-yocto/6.12: update CVE exclusions (6.12.63)
  linux-yocto/6.18: libpf prepare for new glibc
  linux-yocto/6.18: update to v6.18.3
  linux-yocto/6.18: update CVE exclusions (6.18.3)
  linux-yocto/6.18: mtd: use refcount to prevent corruption

 OE-core:
 meta/recipes-kernel/linux/cve-exclusion_6.12.inc   |   380 +-
 meta/recipes-kernel/linux/cve-exclusion_6.18.inc   | 12024 +++++++++++--------
 meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb   |     6 +-
 meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb   |     6 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb |     6 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb |     6 +-
 meta/recipes-kernel/linux/linux-yocto_6.12.bb      |    28 +-
 meta/recipes-kernel/linux/linux-yocto_6.18.bb      |    24 +-
 8 files changed, 7168 insertions(+), 5312 deletions(-)

Comments

Kevin Hao Jan. 7, 2026, 12:53 p.m. UTC | #1
On Tue, Jan 06, 2026 at 10:23:45AM -0500, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Hi all,
> 
> I'm still tweaking my pull request scripts for the split repositories,
> so apologies if something doesn't look quite right.
> 
> I'm unable to push to openembedded-contrib right now, so this is a
> patch only send.
> 
> We are getting closer to removing 6.16 (and then 6.12) from oe-core
> master. These updates should address some config warnings, and
> otherwise improve stability.
> 
> We need to get the reference platforms update to 6.18, so I've cc'
> kevin@windriver to see if he has any plans or comments on that.

The v6.18 kernel triggers an RTNL assertion call trace on my BBB board.
Although this does not block the boot process, I would like to investigate
further to identify the root cause, which may take several days.  However,
since it does not affect normal booting, I can update the default kernel to
v6.18 for the reference board first and debug this issue concurrently, if you prefer.

Thanks,
Kevin
Bruce Ashfield Jan. 7, 2026, 1:59 p.m. UTC | #2
On Wed, Jan 7, 2026 at 7:53 AM Kevin Hao <haokexin@gmail.com> wrote:

> On Tue, Jan 06, 2026 at 10:23:45AM -0500, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Hi all,
> >
> > I'm still tweaking my pull request scripts for the split repositories,
> > so apologies if something doesn't look quite right.
> >
> > I'm unable to push to openembedded-contrib right now, so this is a
> > patch only send.
> >
> > We are getting closer to removing 6.16 (and then 6.12) from oe-core
> > master. These updates should address some config warnings, and
> > otherwise improve stability.
> >
> > We need to get the reference platforms update to 6.18, so I've cc'
> > kevin@windriver to see if he has any plans or comments on that.
>
> The v6.18 kernel triggers an RTNL assertion call trace on my BBB board.
> Although this does not block the boot process, I would like to investigate
> further to identify the root cause, which may take several days.  However,
> since it does not affect normal booting, I can update the default kernel to
> v6.18 for the reference board first and debug this issue concurrently, if
> you prefer.
>

No rush. Whichever is easiest for you, I appreciate the assistance
on this, and if there's anything I can do, let me know.

Bruce



>
> Thanks,
> Kevin
>