From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH v4 0/4] Fix single-name single-content rule for kernel packages
Date: Fri, 4 Sep 2026 10:31:48 +0200 [thread overview]
Message-ID: <288a3ddd-2e91-482d-af8c-b2bcfadd2d1f@ilbers.de> (raw)
In-Reply-To: <20260826131457.1702004-1-felix.moessbauer@siemens.com>
Bumped the hash in p3 and applied to next, thanks.
Zhihang
On 8/26/26 15:14, Felix Moessbauer wrote:
> Similar to upstream Debian, our kernel source packages are (among others)
> architecture specific. By that, we also have to encode the architecture
> (or machine) in the name of the package. Otherwise existing packages might
> get reused on rebuilds with other targets (or multiarch)
>
> In isar, this has ever been modeled incorrectly (the kernels .dsc file
> was arch=any despite being arch specific). This is easy to fix, but
> also depending on the kernels was done incorrectly (a KERNEL_NAME =
> mainline is not specific enough, as mainline on arm64 is technically a
> different kernel (source package) than mainline on amd64.
>
> Patch 4 carries the implementation of option (1) from [1].
>
> [1] https://groups.google.com/g/isar-users/c/JmB2FuEXZBU/m/azKokFVsAwAJ
>
> The series has been tested in -t cross, -t kernel CI.
>
> Changes since v3:
>
> - rebased onto next
> - drop p3 ("kernel: make source package architecture specific") as not
> strictly needed and breaks module build on generic kernels
>
> Changes since v2:
>
> - improve commit messages according to Jan's feedback
> - improve API changelog
> - p2: drop redundant x86_64_defconfig
>
> Changes since v1:
>
> - no functional change
> - rework API changelog and user manual
>
> Best regards,
> Felix Moessbauer
> Siemens AG
>
> Felix Moessbauer (4):
> testsuite: make test_libc_dev_deploy KERNEL_NAME agnostic
> kernel: bind x86_64_defconfig to amd64 architecture instead of machine
> kernel: move common parts of linux-mainline to inc
> kernel: use architecture specific names for kernels
>
> RECIPE-API-CHANGELOG.md | 4 ++
> doc/user_manual.md | 13 +++++-
> meta-isar/conf/machine/beagleplay.conf | 2 +-
> meta-isar/conf/machine/de0-nano-soc.conf | 2 +-
> meta-isar/conf/machine/hikey.conf | 2 +-
> meta-isar/conf/machine/qemuamd64-cip.conf | 2 +-
> meta-isar/conf/machine/sifive-fu540.conf | 2 +-
> meta-isar/conf/machine/stm32mp15x.conf | 2 +-
> .../linux/linux-cip_4.4.166-cip29.bb | 7 ++-
> .../recipes-kernel/linux/linux-mainline.inc | 45 +++++++++++++++++++
> .../linux/linux-mainline_6.12.103.bb | 39 +---------------
> .../linux/linux-phy_6.12.103.bb | 2 +-
> testsuite/citest.py | 23 +++++++---
> 13 files changed, 91 insertions(+), 54 deletions(-)
> create mode 100644 meta-isar/recipes-kernel/linux/linux-mainline.inc
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/288a3ddd-2e91-482d-af8c-b2bcfadd2d1f%40ilbers.de.
prev parent reply other threads:[~2026-09-04 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 13:14 'Felix Moessbauer' via isar-users
2026-08-26 13:14 ` [PATCH v4 1/4] testsuite: make test_libc_dev_deploy KERNEL_NAME agnostic 'Felix Moessbauer' via isar-users
2026-08-26 13:14 ` [PATCH v4 2/4] kernel: bind x86_64_defconfig to amd64 architecture instead of machine 'Felix Moessbauer' via isar-users
2026-08-26 13:14 ` [PATCH v4 3/4] kernel: move common parts of linux-mainline to inc 'Felix Moessbauer' via isar-users
2026-08-27 13:05 ` Zhihang Wei
2026-08-28 6:26 ` 'MOESSBAUER, Felix' via isar-users
2026-08-28 14:50 ` Zhihang Wei
2026-08-26 13:14 ` [PATCH v4 4/4] kernel: use architecture specific names for kernels 'Felix Moessbauer' via isar-users
2026-09-04 8:31 ` Zhihang Wei [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=288a3ddd-2e91-482d-af8c-b2bcfadd2d1f@ilbers.de \
--to=wzh@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--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