From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 09/12] linux-yocto/6.1: cfg: restore CONFIG_DEVMEM
Date: Wed, 8 Nov 2023 09:16:27 -0500 [thread overview]
Message-ID: <d252de6f1ea1e643cc7e5cff38085cf8ce58fc87.1699452828.git.bruce.ashfield@gmail.com> (raw)
In-Reply-To: <cover.1699452828.git.bruce.ashfield@gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Integrating the following commit(s) to linux-yocto/.:
1/1 [
Author: C. Andy Martin
Email: cam@myfastmail.com
Subject: security.cfg: restore strict-only /dev/mem access
Date: Fri, 27 Oct 2023 11:22:06 -0400
CONFIG_DEVMEM was mistakenly not enabled, which defeats
CONFIG_STRICT_DEVMEM and friends, as it completely removes all
/dev/mem support.
Signed-off-by: C. Andy Martin <cam@myfastmail.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.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto-tiny_6.1.bb | 2 +-
meta/recipes-kernel/linux/linux-yocto_6.1.bb | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.1.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.1.bb
index 6ebf533bb0..408fac718e 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.1.bb
@@ -15,7 +15,7 @@ python () {
}
SRCREV_machine ?= "0dad5306907b9e6fb89103dfba80dbd0edafcdb6"
-SRCREV_meta ?= "0553e01ca003e82d32d9b85c0275568e8ce67274"
+SRCREV_meta ?= "3ec1b83af3b59f07cf04e1264fbd30fe2f2f873b"
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.1;destsuffix=${KMETA};protocol=https"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.1.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.1.bb
index af98525c4f..9bf6001353 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.1.bb
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
KCONF_BSP_AUDIT_LEVEL = "2"
SRCREV_machine ?= "780d811bb97bf34f2be6cab28d5a8b099154c40d"
-SRCREV_meta ?= "0553e01ca003e82d32d9b85c0275568e8ce67274"
+SRCREV_meta ?= "3ec1b83af3b59f07cf04e1264fbd30fe2f2f873b"
PV = "${LINUX_VERSION}+git"
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.1.bb b/meta/recipes-kernel/linux/linux-yocto_6.1.bb
index 9f17f244f8..f497ccedd9 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.1.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.1.bb
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "780d811bb97bf34f2be6cab28d5a8b099154c40d"
SRCREV_machine:qemux86-64 ?= "780d811bb97bf34f2be6cab28d5a8b099154c40d"
SRCREV_machine:qemumips64 ?= "9f25eb5709ab8af0ece7306014d5e8b7c6150c68"
SRCREV_machine ?= "780d811bb97bf34f2be6cab28d5a8b099154c40d"
-SRCREV_meta ?= "0553e01ca003e82d32d9b85c0275568e8ce67274"
+SRCREV_meta ?= "3ec1b83af3b59f07cf04e1264fbd30fe2f2f873b"
# 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.34.1
next prev parent reply other threads:[~2023-11-08 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 14:16 [PATCH 00/12] kernel-yocto: consolidated pull request bruce.ashfield
2023-11-08 14:16 ` [PATCH 01/12] linux-yocto/6.5: update to v6.5.8 bruce.ashfield
2023-11-08 14:16 ` [PATCH 02/12] linux-yocto/6.1: update to v6.1.59 bruce.ashfield
2023-11-08 14:16 ` [PATCH 03/12] linux-yocto/6.5: update to v6.5.9 bruce.ashfield
2023-11-08 14:16 ` [PATCH 04/12] linux-yocto/6.1: update to v6.1.60 bruce.ashfield
2023-11-08 14:16 ` [PATCH 05/12] kern-tools: make lower context patches reproducible bruce.ashfield
2023-11-08 14:16 ` [PATCH 06/12] kern-tools: bump SRCREV for queue processing changes bruce.ashfield
2023-11-08 14:16 ` [PATCH 07/12] kern-tools: update SRCREV to include SECURITY.md file bruce.ashfield
2023-11-08 14:16 ` [PATCH 08/12] kernel-yocto: improve metadata patching bruce.ashfield
2023-11-08 14:16 ` bruce.ashfield [this message]
2023-11-08 14:16 ` [PATCH 10/12] linux-yocto/6.5: cfg: restore CONFIG_DEVMEM bruce.ashfield
2023-11-08 14:16 ` [PATCH 11/12] linux-yocto/6.5: update to v6.5.10 bruce.ashfield
2023-11-08 14:16 ` [PATCH 12/12] linux-yocto/6.1: update to v6.1.61 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=d252de6f1ea1e643cc7e5cff38085cf8ce58fc87.1699452828.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