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 04/14] linux-yocto/6.17: unify qemumips (malta) branches
Date: Thu, 30 Oct 2025 13:12:17 -0400	[thread overview]
Message-ID: <791075f373170e63dcdc95b3d9e6613455bb45f0.1761844161.git.bruce.ashfield@gmail.com> (raw)
In-Reply-To: <cover.1761844161.git.bruce.ashfield@gmail.com>

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

The 6.17+ kernel cache is using a single branch for the mti malta
machines, which are what qemumips* emulate. We update our branch
specification to make them buildable.

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/linux-yocto_6.17.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto_6.17.bb b/meta/recipes-kernel/linux/linux-yocto_6.17.bb
index 2180f0f36f..9d2f51ad41 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.17.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.17.bb
@@ -9,14 +9,14 @@ include recipes-kernel/linux/cve-exclusion_6.17.inc
 # board specific branches
 KBRANCH:qemuarm  ?= "v6.17/standard/arm-versatile-926ejs"
 KBRANCH:qemuarm64 ?= "v6.17/standard/base"
-KBRANCH:qemumips ?= "v6.17/standard/mti-malta32"
+KBRANCH:qemumips ?= "v6.17/standard/mti-malta"
 KBRANCH:qemuppc  ?= "v6.17/standard/qemuppc"
 KBRANCH:qemuriscv64  ?= "v6.17/standard/base"
 KBRANCH:qemuriscv32  ?= "v6.17/standard/base"
 KBRANCH:qemux86  ?= "v6.17/standard/base"
 KBRANCH:qemux86-64 ?= "v6.17/standard/base"
 KBRANCH:qemuloongarch64  ?= "v6.17/standard/base"
-KBRANCH:qemumips64 ?= "v6.17/standard/mti-malta64"
+KBRANCH:qemumips64 ?= "v6.17/standard/mti-malta"
 
 SRCREV_machine:qemuarm ?= "23c78022fc97ea5ebc19ea8fb86d324c23a6fbaa"
 SRCREV_machine:qemuarm64 ?= "d76cb43db46c5d45e25df34484c87f5e545bf4c5"
-- 
2.39.2



  parent reply	other threads:[~2025-10-30 17:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 17:12 [PATCH 00/14] kernel-yocto: consolidated pull request bruce.ashfield
2025-10-30 17:12 ` [PATCH 01/14] linux-yocto: introduce 6.17 reference kernels bruce.ashfield
2025-10-30 17:12 ` [PATCH 02/14] linux-yocto/6.17: update CVE exclusions (6.17.5) bruce.ashfield
2025-10-30 17:12 ` [PATCH 03/14] linux-yocto/6.17: fix qemuarm config audit warning bruce.ashfield
2025-10-30 17:12 ` bruce.ashfield [this message]
2025-10-30 17:12 ` [PATCH 05/14] linux-yocto/6.17: fix rdinit boot warning bruce.ashfield
2025-10-30 17:12 ` [PATCH 06/14] linux-yocto/6.17: update to v6.17.6 bruce.ashfield
2025-10-30 17:12 ` [PATCH 07/14] linux-yocto/6.17: update CVE exclusions (6.17.6) bruce.ashfield
2025-10-30 17:12 ` [PATCH 08/14] linux-yocto/6.12: update to v6.12.53 bruce.ashfield
2025-10-30 17:12 ` [PATCH 09/14] linux-yocto/6.12: update CVE exclusions (6.12.53) bruce.ashfield
2025-10-30 17:12 ` [PATCH 10/14] linux-yocto/6.12: update to v6.12.55 bruce.ashfield
2025-10-30 17:12 ` [PATCH 11/14] linux-yocto/6.12: update CVE exclusions (6.12.55) bruce.ashfield
2025-10-30 17:12 ` [PATCH 12/14] poky: make linux-yocto 6.17 the preferred version bruce.ashfield
2025-10-31  7:34   ` [OE-core] " Mikko Rapeli
2025-10-31 12:44     ` Bruce Ashfield
2025-10-30 17:12 ` [PATCH 13/14] yocto-bsp/6.16: specify genericarm64 SRCREV bruce.ashfield
2025-10-31  7:38   ` [OE-core] " Mikko Rapeli
2025-10-30 17:12 ` [PATCH 14/14] yocto-bsp/6.17: introduce kernel bbappend bruce.ashfield
2025-10-31 16:41 ` [OE-core] [PATCH 00/14] kernel-yocto: consolidated pull request Joao Marcos Costa
2025-10-31 16:46   ` 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=791075f373170e63dcdc95b3d9e6613455bb45f0.1761844161.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