public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <valentin.boudevin@gmail.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v4 2/4] generate-cve-exclusions: Add a .bbclass
Date: Fri, 16 Jan 2026 16:35:53 +0100	[thread overview]
Message-ID: <DFQ4HNJZ6IFE.2JI8LHG9EMVE2@bootlin.com> (raw)
In-Reply-To: <20260115190331.2276779-3-valentin.boudevin@gmail.com>

Hi,

On Thu Jan 15, 2026 at 8:03 PM CET, vboudevin via lists.openembedded.org wrote:
> Add a .bbclass to generate-cve-exclusions to use this script at every
> run.
>
> Two steps for testing:
> 1) Inherit this class in the kernel recipe with "inherit
>    generate-cve-exclusions.bbclass"

If this class is only meant to be used in a kernel recipe, maybe
"kernel-generate-cve-exclusions" would be more appropriate name for it?

Not having "kernel" in it would make the class name sound like it could be used
elsewhere.

Antonin

-- 
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-01-16 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 19:03 [PATCH v4 0/4] generate-cve-exclusions: Add a new bbclass ValentinBoudevin
2026-01-15 19:03 ` [PATCH v4 1/4] generate-cve-exclusions: Add --output-json option ValentinBoudevin
2026-01-15 19:03 ` [PATCH v4 2/4] generate-cve-exclusions: Add a .bbclass ValentinBoudevin
2026-01-16 15:35   ` Antonin Godard [this message]
2026-01-15 19:03 ` [PATCH v4 3/4] generate-cve-exclusions: Move python script ValentinBoudevin
2026-01-15 19:03 ` [PATCH v4 4/4] linux: Add inherit on generate-cve-exclusions ValentinBoudevin
2026-01-15 19:49 ` [OE-core] [PATCH v4 0/4] generate-cve-exclusions: Add a new bbclass Ankur Tyagi

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=DFQ4HNJZ6IFE.2JI8LHG9EMVE2@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=valentin.boudevin@gmail.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