From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: peter.marko@siemens.com,
"simone.p.weiss@posteo.com" <simone.p.weiss@posteo.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] cve-check: Log if CVE_STATUS set but not reported for component
Date: Sat, 24 Feb 2024 15:53:39 +0000 [thread overview]
Message-ID: <78093a8adf422103c337bc090842f5a2de991354.camel@linuxfoundation.org> (raw)
In-Reply-To: <AS1PR10MB56977B0654F86221C1B4A70AFD542@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On Sat, 2024-02-24 at 14:28 +0000, Peter Marko via
lists.openembedded.org wrote:
> Hello,
>
> This change looks like the right way forward, but it will need two
> things first:
> * dissolve cve-extra-exclusions.inc into recipes, as every exclusion
> in that file will generate a warning in all components except the one
> for which the exclusion actually is meant
> * create a (per-recipe) variable to disable it, especially for
> kernels where we have auto-generated exclusion lists which do not
> match NVD DB state
WARN_QA:remove:pn-XXXX = "YYYY"
is possible with the version which was switched to use the central QA
function.
Cheers,
Richard
prev parent reply other threads:[~2024-02-24 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 21:08 [PATCH] cve-check: Log if CVE_STATUS set but not reported for component simone.p.weiss
2024-02-23 21:52 ` [OE-core] " Yoann CONGAL
2024-02-24 0:01 ` Simone Weiß
2024-02-24 14:28 ` Marko, Peter
2024-02-24 15:41 ` Simone Weiß
2024-02-24 15:53 ` Richard Purdie [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=78093a8adf422103c337bc090842f5a2de991354.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
--cc=simone.p.weiss@posteo.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