From: srinuvasan.a@siemens.com
To: cip-dev@lists.cip-project.org
Cc: jan.kiszka@siemens.com, srinuvasan <srinuvasan.a@siemens.com>
Subject: [isar-cip-core][PATCH] update cip-kernel-defconfig to the latest version
Date: Fri, 14 Feb 2025 11:01:27 +0530 [thread overview]
Message-ID: <20250214053127.1152501-1-srinuvasan.a@siemens.com> (raw)
From: srinuvasan <srinuvasan.a@siemens.com>
This revision brings the CONFIG_EFIVAR_FS to read
the EFI (Extensible Firmware Interface) variable information via sysfs.
Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
---
recipes-kernel/linux/cip-kernel-config.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/recipes-kernel/linux/cip-kernel-config.inc b/recipes-kernel/linux/cip-kernel-config.inc
index 53bee8f..e761957 100644
--- a/recipes-kernel/linux/cip-kernel-config.inc
+++ b/recipes-kernel/linux/cip-kernel-config.inc
@@ -1,7 +1,7 @@
#
# CIP Core, generic profile
#
-# Copyright (c) Siemens AG, 2022-2024
+# Copyright (c) Siemens AG, 2022-2025
#
# Authors:
# Jan Kiszka <jan.kiszka@siemens.com>
@@ -14,7 +14,7 @@ SRC_URI:append = " ${@ \
if d.getVar('USE_CIP_KERNEL_CONFIG') == '1' else '' \
}"
-SRCREV_cip-kernel-config ?= "e486c93a916cb6f78b4917b7345e8818f96069f9"
+SRCREV_cip-kernel-config ?= "6b5db480b7a43e0217b1fa58f487f0bb997743c7"
do_fetch[vardeps] += "SRCREV_cip-kernel-config"
--
2.39.5
next reply other threads:[~2025-02-14 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 5:31 srinuvasan.a [this message]
2025-02-14 8:17 ` [isar-cip-core][PATCH] update cip-kernel-defconfig to the latest version Jan Kiszka
2025-02-17 5:37 ` Arjunan, Srinu
2025-02-17 9:05 ` Quirin Gylstorff
2025-02-17 9:15 ` Jan Kiszka
2025-02-17 9:26 ` Quirin Gylstorff
2025-02-18 9:33 ` [cip-dev] " Quirin Gylstorff
2025-02-18 11:00 ` Jan Kiszka
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=20250214053127.1152501-1-srinuvasan.a@siemens.com \
--to=srinuvasan.a@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.