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/6] linux-yocto: consolidated pull request
Date: Mon, 14 Oct 2024 09:45:31 -0400	[thread overview]
Message-ID: <cover.1728912923.git.bruce.ashfield@gmail.com> (raw)

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

Richard,

Here's the -stable updates I've been collecting for 6.10 and 6.6.

I'm also bumping -dev to 6.12, even though core-image-kernel-dev
isn't quite ready yet (lttng-modules hasn't updated for 6.12), but
all basic sanity tests have passed.

I'll follow up in a bit with some non-version bump changes that
I still have under test.

Cheers,

Bruce


The following changes since commit ca52444cb62fd595bb50ee14d21ecbc56056129c:

  kernel/reproducibility: factor kernel source epoch for common use (2024-10-14 09:27:37 -0400)

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 (6):
  linux-yocto-dev: conditionally add coreutils to depends
  linux-yocto/6.10: update to v6.10.12
  linux-yocto/6.10: update to v6.10.13
  linux-yocto-dev: bump to v6.12
  linux-yocto/6.6: update to v6.6.54
  linux-yocto/6.10: update to v6.10.14

 meta/recipes-kernel/linux/linux-yocto-dev.bb  |  8 ++++--
 .../linux/linux-yocto-rt_6.10.bb              |  6 ++--
 .../linux/linux-yocto-rt_6.6.bb               |  6 ++--
 .../linux/linux-yocto-tiny_6.10.bb            |  6 ++--
 .../linux/linux-yocto-tiny_6.6.bb             |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_6.10.bb | 28 +++++++++----------
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  | 28 +++++++++----------
 7 files changed, 46 insertions(+), 42 deletions(-)

-- 
2.39.2



             reply	other threads:[~2024-10-14 13:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 13:45 bruce.ashfield [this message]
2024-10-14 13:45 ` [PATCH 1/6] linux-yocto-dev: conditionally add coreutils to depends bruce.ashfield
2024-10-14 17:15   ` [OE-core] " Quentin Schulz
2024-10-15 14:15   ` Richard Purdie
2024-10-15 20:56     ` Bruce Ashfield
2024-10-15 21:01       ` Richard Purdie
2024-10-15 21:09         ` Bruce Ashfield
2024-10-14 13:45 ` [PATCH 2/6] linux-yocto/6.10: update to v6.10.12 bruce.ashfield
2024-10-14 13:45 ` [PATCH 3/6] linux-yocto/6.10: update to v6.10.13 bruce.ashfield
2024-10-14 13:45 ` [PATCH 4/6] linux-yocto-dev: bump to v6.12 bruce.ashfield
2024-10-14 13:45 ` [PATCH 5/6] linux-yocto/6.6: update to v6.6.54 bruce.ashfield
2024-10-14 13:45 ` [PATCH 6/6] linux-yocto/6.10: update to v6.10.14 bruce.ashfield
  -- strict thread matches above, loose matches on Subject: below --
2026-01-14 17:24 [PATCH 0/6] linux-yocto: consolidated pull request bruce.ashfield
2021-03-05  3:54 Bruce Ashfield
2021-02-18  3:59 Bruce Ashfield
2020-09-14 22:34 Bruce Ashfield
2018-10-17 13:38 Bruce Ashfield
2016-07-07 18:39 Bruce Ashfield
2016-06-13 15:56 Bruce Ashfield
2015-10-23 20:18 Bruce Ashfield
2015-08-24 13:51 Bruce Ashfield
2014-10-01  4:43 Bruce Ashfield
2014-05-05 14:10 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.1728912923.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