openembedded-core.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [meta][PATCH 01/05] linux-yocto/7.2: menuconfig,mconf-cfg: Fix broken menuconfig outside of Yocto env
Date: Mon,  7 Sep 2026 21:17:26 -0400	[thread overview]
Message-ID: <20260908011731.2895743-2-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260908011731.2895743-1-bruce.ashfield@gmail.com>

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

Integrating the following commit(s) to linux-yocto/7.2:

1/1 [
    Author: Roland Kovacs
    Email: roland.kovacs@est.tech
    Subject: menuconfig,mconf-cfg: Fix broken menuconfig outside of Yocto env
    Date: Wed, 2 Sep 2026 09:51:58 -0400

    Due to an upstream change running menuconfig fails with:
    	$ make menuconfig
    	scripts/kconfig/mconf-cfg.sh: 12: CROSS_CURSES_LIB: parameter not set

    Fix the error by checking against CROSS_CURSES_LIB with undefined var defaulting
    explicitly to empty string.

    Fixes: 01505857ec741 ("menuconfig,mconf-cfg: Allow specification of ncurses location")
    Ref: https://lore.kernel.org/linux-kbuild/20240611160938.3511096-1-masahiroy@kernel.org/

    Signed-off-by: Roland Kovacs <roland.kovacs@est.tech>
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 .../linux/linux-yocto-rt_7.2.bb               |  4 ++--
 .../linux/linux-yocto-tiny_7.2.bb             |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_7.2.bb  | 20 +++++++++----------
 3 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_7.2.bb b/meta/recipes-kernel/linux/linux-yocto-rt_7.2.bb
index 503a0ee260..fc76baf359 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_7.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_7.2.bb
@@ -15,8 +15,8 @@ python () {
         raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "3d984c8bbdb878fc240fdf9b59892e56802b278d"
-SRCREV_meta ?= "48dd3364f8af7104c75e86ea3c2bd0e55352b59b"
+SRCREV_machine ?= "97c8cde82374f1359a27f1bca7783406a8c58a7f"
+SRCREV_meta ?= "03cb449bc3f6a9ce9599e2b3fb4ad2b3fc0c0b85"
 
 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-7.2;destsuffix=${KMETA};protocol=https"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_7.2.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_7.2.bb
index 6478274956..76521bf9fc 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_7.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_7.2.bb
@@ -18,8 +18,8 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine ?= "eaf351389aa8a14680ad327afecb5abb78347081"
-SRCREV_meta ?= "48dd3364f8af7104c75e86ea3c2bd0e55352b59b"
+SRCREV_machine ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
+SRCREV_meta ?= "03cb449bc3f6a9ce9599e2b3fb4ad2b3fc0c0b85"
 
 PV = "${LINUX_VERSION}+git"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_7.2.bb b/meta/recipes-kernel/linux/linux-yocto_7.2.bb
index 98f1041a46..1decf0c608 100644
--- a/meta/recipes-kernel/linux/linux-yocto_7.2.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_7.2.bb
@@ -17,18 +17,18 @@ KBRANCH:qemux86-64 ?= "v7.2/standard/base"
 KBRANCH:qemuloongarch64  ?= "v7.2/standard/base"
 KBRANCH:qemumips64 ?= "v7.2/standard/mti-malta"
 
-SRCREV_machine:qemuarm ?= "6390ad2592faab51e5930cdcd4073805ebeb3096"
-SRCREV_machine:qemuarm64 ?= "eaf351389aa8a14680ad327afecb5abb78347081"
-SRCREV_machine:qemuloongarch64 ?= "eaf351389aa8a14680ad327afecb5abb78347081"
+SRCREV_machine:qemuarm ?= "d4b8eb4a386a99edc670c6a988b30c6470975013"
+SRCREV_machine:qemuarm64 ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
+SRCREV_machine:qemuloongarch64 ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
 SRCREV_machine:qemumips ?= "ab0e33fefa2a3d0366b2b8deb7cfb3be2d8dc436"
-SRCREV_machine:qemuppc ?= "eaf351389aa8a14680ad327afecb5abb78347081"
-SRCREV_machine:qemuriscv64 ?= "eaf351389aa8a14680ad327afecb5abb78347081"
-SRCREV_machine:qemuriscv32 ?= "eaf351389aa8a14680ad327afecb5abb78347081"
-SRCREV_machine:qemux86 ?= "eaf351389aa8a14680ad327afecb5abb78347081"
-SRCREV_machine:qemux86-64 ?= "eaf351389aa8a14680ad327afecb5abb78347081"
+SRCREV_machine:qemuppc ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
+SRCREV_machine:qemuriscv64 ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
+SRCREV_machine:qemuriscv32 ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
+SRCREV_machine:qemux86 ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
+SRCREV_machine:qemux86-64 ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
 SRCREV_machine:qemumips64 ?= "ab0e33fefa2a3d0366b2b8deb7cfb3be2d8dc436"
-SRCREV_machine ?= "eaf351389aa8a14680ad327afecb5abb78347081"
-SRCREV_meta ?= "48dd3364f8af7104c75e86ea3c2bd0e55352b59b"
+SRCREV_machine ?= "6a8c7c1a4e71cb451c93ec975591179856cf885d"
+SRCREV_meta ?= "03cb449bc3f6a9ce9599e2b3fb4ad2b3fc0c0b85"
 
 # 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.43.0



  reply	other threads:[~2026-09-08  1:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08  1:17 [PATCH 0/5] linux-yocto: -stable updates bruce.ashfield
2026-09-08  1:17 ` bruce.ashfield [this message]
2026-09-08  1:17 ` [meta][PATCH 02/05] linux-yocto/7.2: rt: update to v7.2-rt5 bruce.ashfield
2026-09-08  1:17 ` [meta][PATCH 03/05] linux-yocto/6.18: rt: update to v6.18.37-rt6 bruce.ashfield
2026-09-08  1:17 ` [meta][PATCH 04/05] linux-yocto/7.2: update to v7.2.4 bruce.ashfield
2026-09-08  1:17 ` [meta-yocto-bsp][PATCH 05/05] yocto-bsps: " bruce.ashfield
2026-09-08  1:32   ` Patchtest results for " patchtest
2026-09-08  8:15 ` [OE-core] [PATCH 0/5] linux-yocto: -stable updates Yoann Congal
2026-09-08  9:22   ` Richard Purdie
2026-09-08  9:26   ` Yoann Congal

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=20260908011731.2895743-2-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;
as well as URLs for NNTP newsgroup(s).