From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <rybczynska@gmail.com>
Cc: <docs@lists.yoctoproject.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 11/11] migration-guides/release-notes-5.2: update for upcoming 5.2 release
Date: Tue, 18 Mar 2025 09:00:49 +0100 [thread overview]
Message-ID: <D8J8FMCWVHQO.227FZKDIPIYG4@bootlin.com> (raw)
In-Reply-To: <CAApg2=Ro3uY7tFWHGgLuuEacrXyFTZET4CL6emPaViviFLqQwQ@mail.gmail.com>
Hi Marta,
On Tue Mar 18, 2025 at 7:50 AM CET, Marta Rybczynska via lists.yoctoproject.org wrote:
> On Mon, Mar 17, 2025 at 10:06 AM Antonin Godard via lists.yoctoproject.org
> <antonin.godard=bootlin.com@lists.yoctoproject.org> wrote:
>
>>
>>
>> + - The ``cve-update-db-native`` was restored from kirkstone and can be
>> used
>> + to update the CVE National Vulnerability Database (NVD). Add
>> support for
>> + the FKIE-CAD (https://github.com/fkie-cad/nvd-json-data-feeds) CVE
>> source
>> + for it.
>> +
>>
>
> Could you add something like:
>
> Users can control the NVD database source using the NVD_DB_VERSION variable
> with possible
> values NVD1, NVD2, or FKIE.
Yes, I added this in the reference manual but forgot to mention here.
Will do in v2.
Thanks!
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-03-18 8:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 9:06 [PATCH 00/11] Updates for upcoming 5.2 release Antonin Godard
2025-03-17 9:06 ` [PATCH 01/11] ref-manual/classes.rst: document the ptest-python-pytest class and variables Antonin Godard
2025-03-17 9:06 ` [PATCH 02/11] ref-manual/variables.rst: WATCHDOG_TIMEOUT: fix recipe name Antonin Godard
2025-03-17 9:06 ` [PATCH 03/11] ref-manual/variables.rst: document the WATCHDOG_RUNTIME_SEC variable Antonin Godard
2025-03-17 9:06 ` [PATCH 04/11] ref-manual/variables.rst: document the MOUNT_GROUP variable Antonin Godard
2025-03-17 9:06 ` [PATCH 05/11] ref-manual/features.rst: drop ld-is-gold Antonin Godard
2025-03-17 9:06 ` [PATCH 06/11] ref-manual/variables.rst: document the MESON_INSTALL_TAGS Antonin Godard
2025-03-17 9:06 ` [PATCH 07/11] ref-manual/variables.rst: document the NVD_DB_VERSION variable Antonin Godard
2025-03-17 9:06 ` [PATCH 08/11] migration-guides/migration-5.2.rst: add information about autotools changes Antonin Godard
2025-03-17 9:06 ` [PATCH 09/11] ref-manual/variables.rst: add a link for BB_USE_HOME_NPMRC Antonin Godard
2025-03-17 9:06 ` [PATCH 10/11] migration-guides/migration-5.2: update for upcoming 5.2 release Antonin Godard
2025-03-17 9:06 ` [PATCH 11/11] migration-guides/release-notes-5.2: " Antonin Godard
2025-03-18 6:50 ` [docs] " Marta Rybczynska
2025-03-18 8:00 ` Antonin Godard [this message]
2025-03-18 8:47 ` 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=D8J8FMCWVHQO.227FZKDIPIYG4@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--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