From: "Adivi, Sai Sree Kartheek" <s-adivi@ti.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, <cip-dev@lists.cip-project.org>
Subject: Re: [isar-cip-core][PATCH v2 3/5] Expose kernel branch head recipes via kas option and Kconfig
Date: Wed, 28 May 2025 19:33:38 +0530 [thread overview]
Message-ID: <b37a0484-2775-4bf2-a5d1-739cc3c251d2@ti.com> (raw)
In-Reply-To: <5f42c016426fb5ce955c4eae42a9fbc0c041c8c5.1748011667.git.jan.kiszka@siemens.com>
On 5/23/2025 8:17 PM, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> The kas option file adjusts the PREFERRED_VERSION for the CIP kernel so
> that the corresponding head recipe is selected. This avoids having to
> define an option for each kernel version series.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Acked-by: Sai Sree Kartheek Adivi <s-adivi@ti.com>
> ---
> Kconfig | 11 +++++++++++
> kas/opt/kernel-head.yml | 18 ++++++++++++++++++
> 2 files changed, 29 insertions(+)
> create mode 100644 kas/opt/kernel-head.yml
>
> diff --git a/Kconfig b/Kconfig
> index 0887125a..18560292 100644
> --- a/Kconfig
> +++ b/Kconfig
> @@ -113,6 +113,17 @@ config KAS_INCLUDE_KERNEL
> default "kas/opt/6.1.yml" if KERNEL_6_1
> default "kas/opt/6.12.yml" if KERNEL_6_12
>
> +config KERNEL_HEAD
> + bool "Head of selected CIP kernel branch"
> + help
> + Build head of the git branch that corresponds to the selected CIP
> + kernel. May point to an unreleased state.
> +
> +config KAS_INCLUDE_KERNEL_HEAD
> + string
> + default "kas/opt/kernel-head.yml"
> + depends on KERNEL_HEAD
> +
> config KERNEL_RT
> bool "Real-time CIP kernel"
> depends on !ARCH_RISCV64 || KERNEL_6_12
> diff --git a/kas/opt/kernel-head.yml b/kas/opt/kernel-head.yml
> new file mode 100644
> index 00000000..abb4d624
> --- /dev/null
> +++ b/kas/opt/kernel-head.yml
> @@ -0,0 +1,18 @@
> +#
> +# CIP Core, generic profile
> +#
> +# Copyright (c) Siemens, 2025
> +#
> +# Authors:
> +# Jan Kiszka <jan.kiszka@siemens.com>
> +#
> +# SPDX-License-Identifier: MIT
> +#
> +
> +header:
> + version: 14
> +
> +local_conf_header:
> + kernel-version-head: |
> + PREFERRED_VERSION_linux-cip := "${@d.getVar('PREFERRED_VERSION_linux-cip').rsplit('.', 1)[0] + '-cip-head%'}"
> + PREFERRED_VERSION_linux-cip-rt := "${@d.getVar('PREFERRED_VERSION_linux-cip-rt').rsplit('.', 1)[0] + '-cip-head%'}"
next prev parent reply other threads:[~2025-05-28 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 14:47 [isar-cip-core][PATCH v2 0/5] linux-cip: Add support for building branch heads, cleanups Jan Kiszka
2025-05-23 14:47 ` [isar-cip-core][PATCH v2 1/5] linux-cip: Prepare for building from git branches Jan Kiszka
2025-05-28 13:57 ` Adivi, Sai Sree Kartheek
2025-05-23 14:47 ` [isar-cip-core][PATCH v2 2/5] linux-cip: Add support for building head of development branches Jan Kiszka
2025-05-28 14:02 ` Adivi, Sai Sree Kartheek
2025-05-23 14:47 ` [isar-cip-core][PATCH v2 3/5] Expose kernel branch head recipes via kas option and Kconfig Jan Kiszka
2025-05-28 14:03 ` Adivi, Sai Sree Kartheek [this message]
2025-05-23 14:47 ` [isar-cip-core][PATCH v2 4/5] scripts/update-linux-cip.sh: Address shellcheck findings Jan Kiszka
2025-05-23 14:47 ` [isar-cip-core][PATCH v2 5/5] linux-cip: Update to 4.19.325-cip120-rt42 Jan Kiszka
2025-05-28 9:00 ` [isar-cip-core][PATCH v2 0/5] linux-cip: Add support for building branch heads, cleanups Adivi, Sai Sree Kartheek
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=b37a0484-2775-4bf2-a5d1-739cc3c251d2@ti.com \
--to=s-adivi@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox