From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] linux-yocto: pull request (-stable and config)
Date: Wed, 28 May 2025 22:37:44 +0100 [thread overview]
Message-ID: <8378752f319ac4c4bf8d24215563caf14aef304a.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1748456757.git.bruce.ashfield@gmail.com>
On Wed, 2025-05-28 at 14:28 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> Here's the latest round of linux-yocot stable updates.
>
> I've been sort of following the kernel CVE update series that
> have been floating around.
Thanks. I'll queue them for testing.
>
> If that format has solidified, if someone reaches out to me,
> I can start updating the CVE exclusions at the same time I do
> the -stable merges.
I think we do need to start running that again as it is active now and
does cause build warnings when out of date.
> Otherwise, this is pretty basic stuff.
>
> I plan on doing an intermediate linux-libc-headers bump until
> I can better predict the version we'll use for the fall release.
Sounds good to me.
Cheers,
Richard
prev parent reply other threads:[~2025-05-28 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 18:28 [PATCH 0/4] linux-yocto: pull request (-stable and config) bruce.ashfield
2025-05-28 18:28 ` [PATCH 1/4] linux-yocto/6.12: update to v6.12.28 bruce.ashfield
2025-05-28 18:28 ` [PATCH 2/4] linux-yocto/6.12: update to v6.12.29 bruce.ashfield
2025-05-28 18:28 ` [PATCH 3/4] linux-yocto/6.12: riscv config sync bruce.ashfield
2025-05-28 18:28 ` [PATCH 4/4] linux-yocto/6.12: update to v6.12.30 bruce.ashfield
2025-05-28 21:37 ` Richard Purdie [this message]
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=8378752f319ac4c4bf8d24215563caf14aef304a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.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