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 14/15] linux-yocto/5.15: fix CONFIG_CRYPTO_CCM mismatch warnings
Date: Fri, 18 Nov 2022 17:28:58 -0500	[thread overview]
Message-ID: <597dda8ee04f8ab7e2773fc6b4ab80dc2d126ded.1668810409.git.bruce.ashfield@gmail.com> (raw)
In-Reply-To: <cover.1668810409.git.bruce.ashfield@gmail.com>

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

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

    f475b1a9ded qat: fix CONFIG_CRYPTO_CCM mismatch warnings

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_5.15.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
index f80cabe55d..fc1ccd9b39 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.15.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "a0d36398b257c555381e735cd721cd8479d6762d"
-SRCREV_meta ?= "5ca1021282e796e2427f8c7769af524c433fb39d"
+SRCREV_meta ?= "f475b1a9deddbde23f48d7d535abdd5fb133b837"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
index c09f51ce61..087c30b5a5 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
@@ -15,7 +15,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "1c3448ff6cc6d24d16c6ef6065cb642245cac627"
-SRCREV_meta ?= "5ca1021282e796e2427f8c7769af524c433fb39d"
+SRCREV_meta ?= "f475b1a9deddbde23f48d7d535abdd5fb133b837"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.15.bb b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
index 710accc9e2..d5f21daf35 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
@@ -23,7 +23,7 @@ SRCREV_machine:qemux86 ?= "8cd3f1c8dc13e8fa2d9a25ce0285d3526705eea7"
 SRCREV_machine:qemux86-64 ?= "8cd3f1c8dc13e8fa2d9a25ce0285d3526705eea7"
 SRCREV_machine:qemumips64 ?= "ae8ab2e3acaf9e14cd75a6c96f1ba43c66a1babd"
 SRCREV_machine ?= "8cd3f1c8dc13e8fa2d9a25ce0285d3526705eea7"
-SRCREV_meta ?= "5ca1021282e796e2427f8c7769af524c433fb39d"
+SRCREV_meta ?= "f475b1a9deddbde23f48d7d535abdd5fb133b837"
 
 # 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.19.1



  parent reply	other threads:[~2022-11-18 22:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 22:28 [PATCH 00/15][v2] kernel: consolidated pull request bruce.ashfield
2022-11-18 22:28 ` [PATCH 01/15] linux-yocto-dev: bump to v6.0+ bruce.ashfield
2022-11-18 22:28 ` [PATCH 02/15] linux-yocto/5.19: update to v5.19.16 bruce.ashfield
2022-11-18 22:28 ` [PATCH 03/15] linux-yocto/5.15: update to v5.15.74 bruce.ashfield
2022-11-18 22:28 ` [PATCH 04/15] linux-yocto/5.19: update to v5.19.17 bruce.ashfield
2022-11-18 22:28 ` [PATCH 05/15] linux-yocto/5.15: update to v5.15.76 bruce.ashfield
2022-11-18 22:28 ` [PATCH 06/15] linux-yocto/5.19: cfg: intel and vesa updates bruce.ashfield
2022-11-18 22:28 ` [PATCH 07/15] kern-tools: integrate ZFS speedup patch bruce.ashfield
2022-11-18 22:28 ` [PATCH 08/15] linux-yocto-dev: bump to v6.1 bruce.ashfield
2022-11-18 22:28 ` [PATCH 09/15] kernel-devsrc: fix for v6.1+ bruce.ashfield
2022-11-18 22:28 ` [PATCH 10/15] lttng-modules: fix build " bruce.ashfield
2022-11-18 22:28 ` [PATCH 11/15] linux-yocto/5.19: security.cfg: remove configs which have been dropped bruce.ashfield
2022-11-18 22:28 ` [PATCH 12/15] linux-yocto/5.15: update to v5.15.78 bruce.ashfield
2022-11-18 22:28 ` [PATCH 13/15] linux-yocto/5.19: fix CONFIG_CRYPTO_CCM mismatch warnings bruce.ashfield
2022-11-18 22:28 ` bruce.ashfield [this message]
2022-11-18 22:28 ` [PATCH 15/15] linux-yocto/5.19: fix elfutils run-backtrace-native-core ptest failure 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=597dda8ee04f8ab7e2773fc6b4ab80dc2d126ded.1668810409.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