Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Benjamin Robin <benjamin.robin@bootlin.com>
To: yoann.congal@smile.fr
Cc: Joao Costa <joaomarcos.costa@bootlin.com>,
	openembedded-core@lists.openembedded.org
Subject: [scarthgap] SPDX3, lz4 and avahi: Patches status
Date: Fri, 08 May 2026 14:57:23 +0200	[thread overview]
Message-ID: <Mj30OkfVRxGpGbLR46KjAA@bootlin.com> (raw)

Hello Yoann,

Today I checked the status on patchwork of all the patches that I sent.
I noticed that 3 patches, which I forgot to monitor, are currently stuck in
the following state: Awaiting Upstream.

Do you have any information about it?

meta: fix generation of kernel CONFIG_ in SPDX3
 - https://patchwork.yoctoproject.org/project/oe-core/patch/20260303-backport-fixes-scarthgap-v1-3-2dc803f921a9@bootlin.com/
 - https://lore.kernel.org/all/20260303-backport-fixes-scarthgap-v1-3-2dc803f921a9@bootlin.com/

lz4: Remove a reference to the rejected CVE-2025-62813
 - https://patchwork.yoctoproject.org/project/oe-core/patch/20260303-backport-fixes-scarthgap-v1-2-2dc803f921a9@bootlin.com/
 - https://lore.kernel.org/all/20260303-backport-fixes-scarthgap-v1-2-2dc803f921a9@bootlin.com/

avahi: Remove a reference to the rejected CVE-2021-36217
 - https://patchwork.yoctoproject.org/project/oe-core/patch/20260303-backport-fixes-scarthgap-v1-1-2dc803f921a9@bootlin.com/
 - https://lore.kernel.org/all/20260303-backport-fixes-scarthgap-v1-1-2dc803f921a9@bootlin.com/

Best regards,
-- 
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com





             reply	other threads:[~2026-05-08 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 12:57 Benjamin Robin [this message]
2026-05-18 12:26 ` [scarthgap] SPDX3, lz4 and avahi: Patches status Yoann Congal
2026-06-14 10:37   ` Benjamin Robin

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=Mj30OkfVRxGpGbLR46KjAA@bootlin.com \
    --to=benjamin.robin@bootlin.com \
    --cc=joaomarcos.costa@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=yoann.congal@smile.fr \
    /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