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: [meta][PATCH 01/11] linux-yocto/6.18: genericarm64: enable additional qcom drivers
Date: Mon, 23 Mar 2026 09:50:47 -0400	[thread overview]
Message-ID: <20260323135057.1605923-2-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260323135057.1605923-1-bruce.ashfield@gmail.com>

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

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

1/2 [
    Author: Srinivas Naik Banavathu
    Email: snb@qti.qualcomm.com
    Subject: genericarm64-pinctrl.cfg: enable CONFIG_PINCTRL_QCS8300
    Date: Fri, 20 Feb 2026 15:53:42 +0530

    Enable QCS8300 pin controller driver

    Signed-off-by: Srinivas Naik Banavathu <snb@qti.qualcomm.com>
    Cc: Bruce Ashfield bruce.ashfield@gmail.com
    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

2/2 [
    Author: Srinivas Naik Banavathu
    Email: snb@qti.qualcomm.com
    Subject: genericarm64.cfg: enable CONFIG_INTERCONNECT_QCOM_QCS8300
    Date: Fri, 20 Feb 2026 15:53:43 +0530

    Enable QCS8300 interconnect driver

    Signed-off-by: Srinivas Naik Banavathu <snb@qti.qualcomm.com>
    Cc: Bruce Ashfield bruce.ashfield@gmail.com
    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.18.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.18.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb
index ae06d6ed0d..1b0eb015fe 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.18.bb
@@ -16,7 +16,7 @@ python () {
 }
 
 SRCREV_machine ?= "9bd60c36af4be5a5905bb5408325961475e66880"
-SRCREV_meta ?= "9b173d3a50825b8bffbb62ac6e504a7a56312e2e"
+SRCREV_meta ?= "0b1ea0e509501b1bd4ba5ea8ccb2f3daf525ddec"
 
 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.18;destsuffix=${KMETA};protocol=https"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb
index 619fc8a59c..6782de4950 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.18.bb
@@ -19,7 +19,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "c9dde4c9d33d3635d3c6604a1bb0c62ea01b0f44"
-SRCREV_meta ?= "9b173d3a50825b8bffbb62ac6e504a7a56312e2e"
+SRCREV_meta ?= "0b1ea0e509501b1bd4ba5ea8ccb2f3daf525ddec"
 
 PV = "${LINUX_VERSION}+git"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.18.bb b/meta/recipes-kernel/linux/linux-yocto_6.18.bb
index f5ad28780e..a74520fcaa 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.18.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.18.bb
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "c9dde4c9d33d3635d3c6604a1bb0c62ea01b0f44"
 SRCREV_machine:qemux86-64 ?= "c9dde4c9d33d3635d3c6604a1bb0c62ea01b0f44"
 SRCREV_machine:qemumips64 ?= "9fb4ff0187c85426f21fd40d4c61b742800f65c4"
 SRCREV_machine ?= "c9dde4c9d33d3635d3c6604a1bb0c62ea01b0f44"
-SRCREV_meta ?= "9b173d3a50825b8bffbb62ac6e504a7a56312e2e"
+SRCREV_meta ?= "0b1ea0e509501b1bd4ba5ea8ccb2f3daf525ddec"
 
 # 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-03-23 13:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 13:50 [PATCH 0/11] linux-yocto: consolidated pull request bruce.ashfield
2026-03-23 13:50 ` bruce.ashfield [this message]
2026-03-23 13:50 ` [meta][PATCH 02/11] linux-yocto/6.18: genericarm64: fix configuration audit warning bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 03/11] linux-yocto/6.18: update to v6.18.16 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 04/11] linux-yocto/6.18: update CVE exclusions (6.18.16) bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 05/11] linux-yocto/6.18: update to v6.18.18 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 06/11] linux-yocto/6.18: update CVE exclusions (6.18.18) bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 07/11] linux-yocto-dev: bump to v7.0 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 08/11] linux-yocto/6.18: update to v6.18.19 bruce.ashfield
2026-03-23 22:15   ` Richard Purdie
2026-03-24  0:25     ` Bruce Ashfield
2026-03-23 13:50 ` [meta][PATCH 09/11] linux-yocto/6.18: update CVE exclusions (6.18.19) bruce.ashfield
2026-03-23 13:50 ` [meta-yocto-bsp][PATCH 10/11] yocto-bsps: update to v6.18.18 bruce.ashfield
2026-03-23 14:01   ` Patchtest results for " patchtest
2026-03-23 13:50 ` [meta-yocto-bsp][PATCH 11/11] yocto-bsps: update to v6.18.19 bruce.ashfield
2026-03-23 14:01   ` Patchtest results for " patchtest

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=20260323135057.1605923-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