From: Benjamin ROBIN <benjamin.robin@bootlin.com>
To: Marta Rybczynska <rybczynska@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
thomas.petazzoni@bootlin.com, mathieu.dubois-briand@bootlin.com,
miquel.raynal@bootlin.com, antonin.godard@bootlin.com,
kamel.bouhara@bootlin.com, pascal.eberhard@se.com,
jpewhacker@gmail.com
Subject: Re: [OE-core] [scarthgap v2 0/5] backport: allow to extract all CVE_STATUS info
Date: Fri, 21 Nov 2025 11:42:33 +0100 [thread overview]
Message-ID: <3086109.mvXUDI8C0e@brobin-bootlin> (raw)
In-Reply-To: <CAApg2=SYhNKQrdSM6VNDYzqSbwBrGDB30Za1=TOruk8Dqa=Umw@mail.gmail.com>
Hello Marta,
On Friday, November 21, 2025 at 11:35 AM, Marta Rybczynska wrote:
> Hello Benjamin,
> Do you confirm that this time it is ready for review?
Yes, I confirm this time, this is ready for review :)
Sorry for all the initial noises...
> Kind regards,
> Marta
--
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-11-21 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 9:54 [scarthgap v2 0/5] backport: allow to extract all CVE_STATUS info Benjamin Robin (Schneider Electric)
2025-11-21 9:54 ` [scarthgap v2 1/5] spdx30: provide all CVE_STATUS, not only Patched status Benjamin Robin (Schneider Electric)
2025-11-21 9:54 ` [scarthgap v2 2/5] vex.bbclass: add a new class Benjamin Robin (Schneider Electric)
2025-11-21 9:54 ` [scarthgap v2 3/5] cve-check: extract extending CVE_STATUS to library function Benjamin Robin (Schneider Electric)
2025-11-21 9:54 ` [scarthgap v2 4/5] spdx: extend CVE_STATUS variables Benjamin Robin (Schneider Electric)
2025-11-21 9:54 ` [scarthgap v2 5/5] vex: fix rootfs manifest Benjamin Robin (Schneider Electric)
2025-11-21 10:35 ` [OE-core] [scarthgap v2 0/5] backport: allow to extract all CVE_STATUS info Marta Rybczynska
2025-11-21 10:42 ` Benjamin ROBIN [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=3086109.mvXUDI8C0e@brobin-bootlin \
--to=benjamin.robin@bootlin.com \
--cc=antonin.godard@bootlin.com \
--cc=jpewhacker@gmail.com \
--cc=kamel.bouhara@bootlin.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pascal.eberhard@se.com \
--cc=rybczynska@gmail.com \
--cc=thomas.petazzoni@bootlin.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