From: Jan Kiszka <jan.kiszka@siemens.com>
To: Badrikesh Prusty <badrikesh.prusty@siemens.com>,
cip-dev@lists.cip-project.org
Subject: Re: [isar-cip-core][PATCH] linux-cip: Update to 6.12.108-cip31
Date: Wed, 9 Sep 2026 13:57:38 +0200 [thread overview]
Message-ID: <2ffed3eb-e025-4425-96d9-315ae2d97077@siemens.com> (raw)
In-Reply-To: <20260907094846.359272-1-badrikesh.prusty@siemens.com>
On 07.09.26 11:48, Badrikesh Prusty wrote:
> Signed-off-by: Badrikesh Prusty <badrikesh.prusty@siemens.com>
> ---
> recipes-kernel/linux/linux-cip-rt_6.12.104-cip30.bb | 1 -
> recipes-kernel/linux/linux-cip-rt_6.12.108-cip31.bb | 1 +
> ...{linux-cip_6.12.104-cip30.bb => linux-cip_6.12.108-cip31.bb} | 2 +-
> 3 files changed, 2 insertions(+), 2 deletions(-)
> delete mode 120000 recipes-kernel/linux/linux-cip-rt_6.12.104-cip30.bb
> create mode 120000 recipes-kernel/linux/linux-cip-rt_6.12.108-cip31.bb
> rename recipes-kernel/linux/{linux-cip_6.12.104-cip30.bb => linux-cip_6.12.108-cip31.bb} (59%)
>
> diff --git a/recipes-kernel/linux/linux-cip-rt_6.12.104-cip30.bb b/recipes-kernel/linux/linux-cip-rt_6.12.104-cip30.bb
> deleted file mode 120000
> index e767cba..0000000
> --- a/recipes-kernel/linux/linux-cip-rt_6.12.104-cip30.bb
> +++ /dev/null
> @@ -1 +0,0 @@
> -linux-cip_6.12.104-cip30.bb
> \ No newline at end of file
> diff --git a/recipes-kernel/linux/linux-cip-rt_6.12.108-cip31.bb b/recipes-kernel/linux/linux-cip-rt_6.12.108-cip31.bb
> new file mode 120000
> index 0000000..6b45063
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-cip-rt_6.12.108-cip31.bb
> @@ -0,0 +1 @@
> +linux-cip_6.12.108-cip31.bb
> \ No newline at end of file
> diff --git a/recipes-kernel/linux/linux-cip_6.12.104-cip30.bb b/recipes-kernel/linux/linux-cip_6.12.108-cip31.bb
> similarity index 59%
> rename from recipes-kernel/linux/linux-cip_6.12.104-cip30.bb
> rename to recipes-kernel/linux/linux-cip_6.12.108-cip31.bb
> index 8b7671f..7373de3 100644
> --- a/recipes-kernel/linux/linux-cip_6.12.104-cip30.bb
> +++ b/recipes-kernel/linux/linux-cip_6.12.108-cip31.bb
> @@ -7,4 +7,4 @@
>
> require linux-cip-release.inc
>
> -SRC_URI[sha256sum] = "d4fbae6f58c86c1a1da3c23e013eab54caf57aa11efb323b98150298cddcbb18"
> +SRC_URI[sha256sum] = "baf5969362189174c1d0b3480bc33defd3b9ccb73af768b811c117c2e16f8244"
Was hoping for more CIP kernel updates, but as these are not ready yet:
Thanks, applied.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
prev parent reply other threads:[~2026-09-09 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 9:48 [isar-cip-core][PATCH] linux-cip: Update to 6.12.108-cip31 Badrikesh Prusty
2026-09-09 11:57 ` 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=2ffed3eb-e025-4425-96d9-315ae2d97077@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=badrikesh.prusty@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox