From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 5/6] linux-yocto/6.12: bsp/genericarm64: modular configuration updates
Date: Tue, 6 May 2025 12:32:59 -0400 [thread overview]
Message-ID: <78b2fdea28be0f38ec52da2aa40b4fb9b9893761.1746548780.git.bruce.ashfield@gmail.com> (raw)
In-Reply-To: <cover.1746548780.git.bruce.ashfield@gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Integrating the following commit(s) to linux-yocto/.:
1/3 [
Author: Bruce Ashfield
Email: bruce.ashfield@gmail.com
Subject: genericarm64: build drivers as modules
Date: Tue, 6 May 2025 09:27:53 -0400
Load on demand. They should not be needed
to run the kernel since it has already been
loaded and firmware has already configured HW
enough to boot into kernel.
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
2/3 [
Author: Mikko Rapeli
Email: mikko.rapeli@linaro.org
Subject: nft_test.cfg: build CONFIG_LEDS_GPIO as module
Date: Tue, 22 Apr 2025 17:38:28 +0300
The driver can be compiled as module.
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
3/3 [
Author: Mikko Rapeli
Email: mikko.rapeli@linaro.org
Subject: nft_test.cfg: build CONFIG_VETH as module
Date: Tue, 22 Apr 2025 17:38:29 +0300
The driver can be compiled as module
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_6.12.bb | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb
index 27bd9f66d8..2211f78cea 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.12.bb
@@ -15,7 +15,7 @@ python () {
}
SRCREV_machine ?= "a20f2b5c8760fc32bd7137fbd952f7f3f810ae26"
-SRCREV_meta ?= "1f6ab68a1d86836bf1b82b791df03da3cfeacb3f"
+SRCREV_meta ?= "e8b9f0530a30d2536429c78676f09189ba5d3a50"
SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.12;destsuffix=${KMETA};protocol=https"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb
index 50a217958d..bfe1773e48 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.12.bb
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
KCONF_BSP_AUDIT_LEVEL = "2"
SRCREV_machine ?= "8bdb46d18b39209344e65cd7ee24d1fa451397d5"
-SRCREV_meta ?= "1f6ab68a1d86836bf1b82b791df03da3cfeacb3f"
+SRCREV_meta ?= "e8b9f0530a30d2536429c78676f09189ba5d3a50"
PV = "${LINUX_VERSION}+git"
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.12.bb b/meta/recipes-kernel/linux/linux-yocto_6.12.bb
index 96954f24a3..b7cfbca475 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.12.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.12.bb
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "8bdb46d18b39209344e65cd7ee24d1fa451397d5"
SRCREV_machine:qemux86-64 ?= "8bdb46d18b39209344e65cd7ee24d1fa451397d5"
SRCREV_machine:qemumips64 ?= "54af295ab3ca402812576c8425d92dcabe9f0b0d"
SRCREV_machine ?= "8bdb46d18b39209344e65cd7ee24d1fa451397d5"
-SRCREV_meta ?= "1f6ab68a1d86836bf1b82b791df03da3cfeacb3f"
+SRCREV_meta ?= "e8b9f0530a30d2536429c78676f09189ba5d3a50"
# set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
# get the <version>/base branch, which is pure upstream -stable, and the same
--
2.39.2
next prev parent reply other threads:[~2025-05-06 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 16:32 [PATCH 0/6] kernel-yocto: consolidated pull request bruce.ashfield
2025-05-06 16:32 ` [PATCH 1/6] kernel-yocto: allow annotated options to be modified bruce.ashfield
2025-05-06 16:32 ` [PATCH 2/6] linux-yocto-dev: update to v6.15 bruce.ashfield
2025-05-06 16:32 ` [PATCH 3/6] linux-yocto/6.12: update to v6.12.24 bruce.ashfield
2025-05-06 16:32 ` [PATCH 4/6] linux-yocto/6.12: update to v6.12.25 bruce.ashfield
2025-05-06 16:32 ` bruce.ashfield [this message]
2025-05-06 16:33 ` [PATCH 6/6] linux-yocto/6.12: update to v6.12.27 bruce.ashfield
2025-05-07 7:42 ` [OE-core] [PATCH 0/6] kernel-yocto: consolidated pull request Mathieu Dubois-Briand
2025-05-07 7:58 ` Richard Purdie
[not found] ` <183D2FC291E34522.16348@lists.openembedded.org>
2025-05-07 11:18 ` Richard Purdie
2025-05-07 11:39 ` Mikko Rapeli
2025-05-07 13:03 ` Bruce Ashfield
2025-05-15 16:06 ` Fabio Estevam
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=78b2fdea28be0f38ec52da2aa40b4fb9b9893761.1746548780.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