From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <peter.marko@siemens.com>,
"Quentin Schulz" <quentin.schulz@cherry.de>,
"docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] vulnerabilities: update nvdcve file name
Date: Mon, 13 Oct 2025 09:15:21 +0200 [thread overview]
Message-ID: <DDH0CO4RNC8X.BPLI3JN7AMHW@bootlin.com> (raw)
In-Reply-To: <AS1PR10MB5697A8FD8430D87D4D7EB560FDECA@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On Sat Oct 11, 2025 at 11:37 PM CEST, Peter Marko via lists.yoctoproject.org wrote:
>
>
>> -----Original Message-----
>> From: Antonin Godard <antonin.godard@bootlin.com>
>> Sent: Tuesday, September 16, 2025 13:07
>> To: Marko, Peter (FT D EU SK BFS1) <Peter.Marko@siemens.com>; Quentin
>> Schulz <quentin.schulz@cherry.de>; docs@lists.yoctoproject.org
>> Subject: Re: [docs] [PATCH] vulnerabilities: update nvdcve file name
>>
>> On Tue Sep 16, 2025 at 12:39 PM CEST, Peter Marko via lists.yoctoproject.org
>> wrote:
>> > Hello,
>> >
>> > I just wanted to say that I'm back from vacation and will try to submit patches
>> for LTS branches still this week.
>>
>> I backported this patch to walnascar, as part of the pull request from Friday
>> last week.
>>
>> I think you could send a separate patch for the new fetcher on scarthgap if you
>> have the time.
>
> I have now sent patches for scarthgap and kirkstone.
> Sorry for the delay.
>
> Peter
Thanks, I applied these on the -next branches.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-10-13 7:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 14:53 [PATCH] vulnerabilities: update nvdcve file name Peter Marko
2025-09-01 9:50 ` [docs] " Quentin Schulz
2025-09-16 10:39 ` Marko, Peter
2025-09-16 11:07 ` Antonin Godard
2025-10-11 21:37 ` Marko, Peter
2025-10-13 7:15 ` Antonin Godard [this message]
2025-09-17 14:13 ` Antonin Godard
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=DDH0CO4RNC8X.BPLI3JN7AMHW@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=peter.marko@siemens.com \
--cc=quentin.schulz@cherry.de \
/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