From: Kevin Hao <haokexin@gmail.com>
To: bruce.ashfield@gmail.com
Cc: richard.purdie@linuxfoundation.org,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/7] linux-yocto: consolidated pull request
Date: Wed, 7 Jan 2026 20:53:47 +0800 [thread overview]
Message-ID: <aV5XW4Rf4tvtJU_O@pek-khao-d3> (raw)
In-Reply-To: <20260106152352.932717-1-bruce.ashfield@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-01-07 12:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:23 [PATCH 0/7] linux-yocto: consolidated pull request bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 01/07] linux-yocto/6.18: genericarm64: remove SLIM_QCOM_CTR bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 02/07] linux-yocto/6.12: update to v6.12.63 bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 03/07] linux-yocto/6.12: update CVE exclusions (6.12.63) bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 04/07] linux-yocto/6.18: libpf prepare for new glibc bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 05/07] linux-yocto/6.18: update to v6.18.3 bruce.ashfield
2026-01-06 15:23 ` [meta][PATCH 07/07] linux-yocto/6.18: mtd: use refcount to prevent corruption bruce.ashfield
2026-01-07 12:53 ` Kevin Hao [this message]
2026-01-07 13:59 ` [PATCH 0/7] linux-yocto: consolidated pull request Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 14:25 bruce.ashfield
2023-12-05 4:26 bruce.ashfield
2022-06-07 13:59 bruce.ashfield
2020-10-06 19:04 Bruce Ashfield
2018-05-18 15:05 Bruce Ashfield
2018-03-27 15:03 Bruce Ashfield
2018-03-28 10:31 ` Burton, Ross
2018-03-28 10:33 ` Burton, Ross
2018-03-28 12:01 ` Bruce Ashfield
2018-03-28 12:07 ` Burton, Ross
2018-03-28 12:57 ` Bruce Ashfield
2018-03-29 12:58 ` Bruce Ashfield
2018-03-29 13:13 ` Richard Purdie
2018-03-29 13:55 ` Bruce Ashfield
2016-11-22 15:58 Bruce Ashfield
2015-05-21 19:08 Bruce Ashfield
2014-09-23 14:57 Bruce Ashfield
2014-09-08 19:55 [PATCH 0/7] linux-yocto*: " Bruce Ashfield
2014-09-09 11:42 ` Burton, Ross
2014-09-09 12:55 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aV5XW4Rf4tvtJU_O@pek-khao-d3 \
--to=haokexin@gmail.com \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox