From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] kernel-yocto: consolidated pull request
Date: Thu, 21 Nov 2024 16:50:24 +0000 [thread overview]
Message-ID: <b9e4809388f7a71ec1d5cf85e6fec7aa1fee65b6.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1732162137.git.bruce.ashfield@gmail.com>
On Wed, 2024-11-20 at 23:13 -0500, bruce.ashfield@gmail.com wrote:
> Here are the -stable bumps that I've gathered. The 6.6 updates will
> help the CVEs in master, but 6.10 will continue to drag for another
> couple of weeks until I'm ready to fully send v6.12 as the new
> reference kernel and I remove it from master.
>
> I've also included a couple of devsrc changes that I previously
> sent (at least I think I previously sent them).
>
> Finally, the biggest change in this pull is the libc-headers update.
> I've tested it against glibc and musl, and didn't find any issues.
> I do expect that something will break, but it needs some extended
> AB testing to weed out any remaining issues.
>
> Getting the libc-headers in early will ease the introduction of
> the 6.12 reference kernel.
>
Thanks for these. So far on the test build there was a genericarm64
warning which Ross has sent a patch for. It is definitely good to get
that headers change in to start with!
I didn't take the devsrc one as it was already merged.
Cheers,
Richard
next prev parent reply other threads:[~2024-11-21 16:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 4:13 [PATCH 0/6] kernel-yocto: consolidated pull request bruce.ashfield
2024-11-21 4:13 ` [PATCH 1/6] kernel-devsrc: update for 6.12+ bruce.ashfield
2024-11-21 4:13 ` [PATCH 2/6] kernel-devsrc: fix powerpc " bruce.ashfield
2024-11-21 4:13 ` [PATCH 3/6] linux-yocto/6.6: update to v6.6.60 bruce.ashfield
2024-11-21 4:13 ` [PATCH 4/6] linux-yocto/6.10: cfg: gpio: allow to re-enable the deprecated GPIO sysfs interface bruce.ashfield
2024-11-21 4:13 ` [PATCH 5/6] linux-libc-headers: update to v6.12 bruce.ashfield
2024-11-21 4:13 ` [PATCH 6/6] linux-yocto/6.6: update to v6.6.62 bruce.ashfield
2024-11-21 16:50 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-08 14:36 [PATCH 0/6] kernel-yocto: consolidated pull request bruce.ashfield
2025-07-09 7:58 ` Richard Purdie
2025-07-09 13:01 ` Bruce Ashfield
2025-05-06 16:32 bruce.ashfield
2024-12-10 21:06 bruce.ashfield
2022-04-04 15:19 bruce.ashfield
2021-07-29 4:49 Bruce Ashfield
2021-06-16 20:48 Bruce Ashfield
2017-07-11 15:04 Bruce Ashfield
2017-06-08 19:21 Bruce Ashfield
2016-08-15 18:26 Bruce Ashfield
2016-08-16 16:00 ` Burton, Ross
2016-08-16 16:01 ` Bruce Ashfield
2016-08-16 16:10 ` Burton, Ross
2016-08-16 16:11 ` Bruce Ashfield
2016-08-16 16:15 ` Burton, Ross
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=b9e4809388f7a71ec1d5cf85e6fec7aa1fee65b6.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