From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: openembedded-core@lists.openembedded.org
Cc: poky@lists.yoctoproject.org, Mikko Rapeli <mikko.rapeli@linaro.org>
Subject: [PATCH 1/3] kern-tools-native: update to support modular kernel builds
Date: Wed, 23 Apr 2025 11:02:44 +0300 [thread overview]
Message-ID: <20250423080246.128723-1-mikko.rapeli@linaro.org> (raw)
After this update scc tool can compile options as modules
conditionally without duplicating config fragments when
the options contain a comment like:
CONFIG_LEDS_GPIO=y # OVERRIDE:$MODULE_OR_Y
Then "scc -DMODULE_OR_Y=m" converts these into
CONFIG_LEDS_GPIO=m
Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>
---
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 6dd19f1f09..20b1bcaf37 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "\
DEPENDS += "git-replacement-native"
-SRCREV = "c8c1f17867d0cc7d04be225ba4901f2373428be2"
+SRCREV = "fe67c98d2e9b74af44d0c4b660fa18e3a95e7edd"
PV = "0.3+git"
inherit native
--
2.43.0
next reply other threads:[~2025-04-23 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 8:02 Mikko Rapeli [this message]
2025-04-23 8:02 ` [PATCH 2/3] kernel-yocto.bbclass: support modular kernel configs Mikko Rapeli
2025-04-23 12:30 ` [poky] " Bruce Ashfield
2025-04-23 12:40 ` Mikko Rapeli
2025-04-23 8:02 ` [PATCH 3/3] linux-yocto: build modular kernel on genericarm64 Mikko Rapeli
2025-04-23 12:31 ` [OE-core] " Bruce Ashfield
2025-04-23 12:31 ` [poky] [PATCH 1/3] kern-tools-native: update to support modular kernel builds 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=20250423080246.128723-1-mikko.rapeli@linaro.org \
--to=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=poky@lists.yoctoproject.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