Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <peter.marko@siemens.com>, <openembedded-core@lists.openembedded.org>
Cc: "Hetvi Thakar" <hthakar@cisco.com>
Subject: Re: [OE-core] [scarthgap][PATCH] u-boot-tools: use all patches from u-boot
Date: Fri, 16 Oct 2026 00:14:56 +0200	[thread overview]
Message-ID: <DM5RBD9MJT2O.2M12R8AMW5OLY@smile.fr> (raw)
In-Reply-To: <20260923173850.21338-1-peter.marko@siemens.com>

On Wed Sep 23, 2026 at 7:38 PM CEST, Peter Marko via lists.openembedded.org wrote:
> From: Peter Marko <peter.marko@siemens.com>
>
> After sharing CVE_PRODUCT between u-boot and u-boot-tools CVEs
> patched in u-boot showed-up in CVE reports for u-boot-tools.
>
> It does not make much sense to share git repository but not share all
> patches on top of it, so move adding all patches from u-boot recipe to a
> common include file where also the git repository is defined.
>
> Signed-off-by: Peter Marko <peter.marko@siemens.com>
> ---
>  meta/recipes-bsp/u-boot/u-boot-common.inc       | 10 ++++++++++
>  meta/recipes-bsp/u-boot/u-boot-tools_2024.01.bb |  2 --
>  meta/recipes-bsp/u-boot/u-boot_2024.01.bb       | 12 ------------
>  3 files changed, 10 insertions(+), 14 deletions(-)

Hello Peter, Hetvi,

There is a bit of back-and-forth around u-boot-common.inc. So I thought I
would give my vision and get your thoughts.

Fundamentally, there is confusion about the usage of this .inc file:
* This is the common part of u-boot and u-boot-tools recipes (what the
  above patch uses)
* But, also, this may be used by downstream layers to reuse u-boot
  recipe parts. We basically did the revert of Peter's patch a few month
  ago for this reason[0].

With Paul, we would like to have a single set of patches common for both
u-boot and u-boot-tools, but that can't be in u-boot-common.inc as there
is a risk of breaking downstream layers.

Our idea is to create a new inc file "u-boot-common-patches.inc" (I'm
not attached to the name) that contains only SRC_URI += "CVE_*.patch"
and a big warning explaining that is file is only supposed to be
included from layer-local recipes (namely u-boot and u-boot-tools).

This whole situation is not ideal but think the above would solve our
issues and still be acceptable under stable policy.

What do you think?

Regards,

[0]: u-boot: move CVE patches out of the common .inc file - openembedded-core - OpenEmbedded Core layer
     https://git.openembedded.org/openembedded-core/commit/?id=f4ced8ff03147dd532a88cf3ce08d61fab057522
-- 
Yoann Congal
Smile ECS



  reply	other threads:[~2026-10-15 22:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 17:38 [scarthgap][PATCH] u-boot-tools: use all patches from u-boot Peter Marko
2026-10-15 22:14 ` Yoann Congal [this message]
2026-10-20  5:16   ` [OE-core] " Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-28  9:07     ` Yoann Congal
2026-10-28 10:04       ` Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-28 10:56         ` Yoann Congal

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=DM5RBD9MJT2O.2M12R8AMW5OLY@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=hthakar@cisco.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.marko@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