All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Subject: [isar-cip-core][PATCH 4/4] linux-cip: Update cip-kernel-config
Date: Tue,  5 Mar 2024 10:07:33 +0100	[thread overview]
Message-ID: <22426e38224aa9dda6f2cd34e64f54c3b8bd446d.1709629653.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1709629653.git.jan.kiszka@siemens.com>

From: Jan Kiszka <jan.kiszka@siemens.com>

This specifically brings the config switches needed for RISC-V in order
to use our SWUpdate integration.

Signed-off-by: Jan Kiszka <jan.kiszka@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 5013eb95..40c378bf 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-2023
+# Copyright (c) Siemens AG, 2022-2024
 #
 # Authors:
 #  Jan Kiszka <jan.kiszka@siemens.com>
@@ -14,4 +14,4 @@ SRC_URI:append = " ${@ \
     if d.getVar('USE_CIP_KERNEL_CONFIG') == '1' else '' \
     }"
 
-SRCREV_cip-kernel-config ?= "8133457d8e156c34eebe52d9affab9df3f7b597f"
+SRCREV_cip-kernel-config ?= "ee86aca8abbe7a41536bcb53142fbf0f57b1c9b7"
-- 
2.35.3



      parent reply	other threads:[~2024-03-05  9:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  9:07 [isar-cip-core][PATCH 0/4] Version updates, snapshot-based RISC-V Jan Kiszka
2024-03-05  9:07 ` [isar-cip-core][PATCH 1/4] linux-cip: Update to 4.19.306-cip107-rt35 and 6.1.80-cip16[-rt9] Jan Kiszka
2024-03-05  9:07 ` [isar-cip-core][PATCH 2/4] Switch sid-based riscv64 back to a snapshot Jan Kiszka
2024-03-05  9:07 ` [isar-cip-core][PATCH 3/4] Update Isar to release 0.10 Jan Kiszka
2024-03-05  9:07 ` Jan Kiszka [this message]

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=22426e38224aa9dda6f2cd34e64f54c3b8bd446d.1709629653.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=cip-dev@lists.cip-project.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 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.