From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-distro: Fix multiple provider warnings
Date: Mon, 03 Jun 2024 09:38:00 +0300 [thread overview]
Message-ID: <6eae347c294237024f7192942c94b3dff2c88a8a.camel@ilbers.de> (raw)
In-Reply-To: <63d67e64-017e-4874-8042-49c2abaa2f17@siemens.com>
On Tue, 2024-05-28 at 15:48 +0200, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> As now all recipe variants of this stub target provide the same, we
> get
> warnings like these when using the distro kernel:
>
> NOTE: Multiple providers are available for linux-image-arm64 (linux-
> distro, linux-distro-native)
> Consider defining a PREFERRED_PROVIDER entry to match linux-image-
> arm64
>
> We can resolve that by limiting the PROVIDES additions to the base
> target again as all of them are stubs anyway, Debian will provide the
> actual packages.
>
> Fixes: b7e3c78766c3 ("module.inc: fix kbuild dependency")
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> meta/recipes-kernel/linux/linux-distro.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-kernel/linux/linux-distro.bb
> b/meta/recipes-kernel/linux/linux-distro.bb
> index 16673b67..d4f6026d 100644
> --- a/meta/recipes-kernel/linux/linux-distro.bb
> +++ b/meta/recipes-kernel/linux/linux-distro.bb
> @@ -6,6 +6,9 @@
> # SPDX-License-Identifier: MIT
>
> python() {
> + if ("class-native" or "class-compat") in
> d.getVar("OVERRIDES").split(":"):
> + return
> +
> distro_kernels = d.getVar('DISTRO_KERNELS') or ""
> for kernel in distro_kernels.split():
> d.appendVar('PROVIDES', ' linux-image-' + kernel)
> --
> 2.43.0
>
Applied to next, thanks.
--
Best regards,
Uladzimir.
prev parent reply other threads:[~2024-06-03 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 13:48 Jan Kiszka
2024-06-03 6:38 ` Uladzimir Bely [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=6eae347c294237024f7192942c94b3dff2c88a8a.camel@ilbers.de \
--to=ubely@ilbers.de \
--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