From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com, Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/5] linux-libc-headers: bump to v6.9
Date: Fri, 31 May 2024 09:31:33 +0100 [thread overview]
Message-ID: <41fd285e01dc6aa107cbb8b29881b10ff964f3aa.camel@linuxfoundation.org> (raw)
In-Reply-To: <c44b4254b0cbc679d548171abbc415a29e4e2b96.1717105222.git.bruce.ashfield@gmail.com>
On Thu, 2024-05-30 at 17:44 -0400, bruce.ashfield@gmail.com wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> ---
> meta/conf/distro/include/tcmode-default.inc | 2 +-
> .../{linux-libc-headers_6.6.bb => linux-libc-headers_6.9.bb} | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.6.bb => linux-libc-headers_6.9.bb} (83%)
I think this is causing a musl/busybox compile issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/9384
but I haven't 100% confirmed that it is this change specifically yet.
Copying Khem.
Cheers,
Richard
next prev parent reply other threads:[~2024-05-31 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 21:44 [PATCH 0/5] kernel-yocto: consolidated pull request bruce.ashfield
2024-05-30 21:44 ` [PATCH 1/5] linux-yocto/6.6: update to v6.6.30 bruce.ashfield
2024-05-30 21:44 ` [PATCH 2/5] linux-yocto/6.6: intel configuration changes bruce.ashfield
2024-05-30 21:44 ` [PATCH 3/5] linux-libc-headers: bump to v6.9 bruce.ashfield
2024-05-31 8:31 ` Richard Purdie [this message]
[not found] ` <17D485A451D95A5E.21428@lists.openembedded.org>
2024-05-31 8:58 ` [OE-core] " Richard Purdie
2024-05-31 12:52 ` Bruce Ashfield
[not found] ` <17D493DFBE920C26.14802@lists.openembedded.org>
2024-05-31 12:59 ` Bruce Ashfield
2024-05-30 21:44 ` [PATCH 4/5] linux-yocto/6.6: update to v6.6.32 bruce.ashfield
2024-05-30 21:44 ` [PATCH 5/5] linux-yocto/6.6: cfg: introduce Intel NPU fragment 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=41fd285e01dc6aa107cbb8b29881b10ff964f3aa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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