public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/5] kernel-yocto: consolidated pull request
Date: Thu, 30 May 2024 17:44:27 -0400	[thread overview]
Message-ID: <cover.1717105222.git.bruce.ashfield@gmail.com> (raw)

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Richard,

A dev kernel bump to 6.10 will follow this, but I still have it under
test.

I've built core-image-kernel-dev and minimal for multiple architectures
against both musl and glibc for the kernel headers and I didn't find
any issues. Fingers crossed the AB doesn't find something I missed.

-stable updates for the LTS branches will follow in a few more days.

Cheers,

Bruce

The following changes since commit f66f8fa9f605d5dc39acb10226198b3ab40dcaa3:

  oe-build-perf-report: Add commit hash link to chart tooltip (2024-05-24 16:59:31 +0100)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib zedd/kernel
  https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  linux-yocto/6.6: update to v6.6.30
  linux-yocto/6.6: intel configuration changes
  linux-libc-headers: bump to v6.9
  linux-yocto/6.6: update to v6.6.32
  linux-yocto/6.6: cfg: introduce Intel NPU fragment

 meta/conf/distro/include/tcmode-default.inc   |  2 +-
 ...aders_6.6.bb => linux-libc-headers_6.9.bb} |  2 +-
 .../linux/linux-yocto-rt_6.6.bb               |  6 ++--
 .../linux/linux-yocto-tiny_6.6.bb             |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  | 28 +++++++++----------
 5 files changed, 22 insertions(+), 22 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.6.bb => linux-libc-headers_6.9.bb} (83%)

-- 
2.39.2



             reply	other threads:[~2024-05-30 21:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 21:44 bruce.ashfield [this message]
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
     [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
  -- strict thread matches above, loose matches on Subject: below --
2025-02-09 23:56 [PATCH 0/5] kernel-yocto: consolidated pull request bruce.ashfield
2024-09-06 17:45 bruce.ashfield
2022-05-19 15:15 bruce.ashfield
2020-08-27 17:53 Bruce Ashfield
2016-11-16 14:24 Bruce Ashfield
2016-09-08  1:08 Bruce Ashfield
2013-02-01 14:02 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=cover.1717105222.git.bruce.ashfield@gmail.com \
    --to=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