From: "vboudevin" <valentin.boudevin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] improve_kerne_cve_report: Add a bbclass support
Date: Thu, 15 Jan 2026 07:41:31 -0800 [thread overview]
Message-ID: <659490.1768491691095926188@lists.openembedded.org> (raw)
In-Reply-To: <PA3PR07MB1072143D325ABB3729C5010D88A85A@PA3PR07MB10721.eurprd07.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
Hi Daniel,
I just pushed a V2 of my patch here: https://lists.openembedded.org/g/openembedded-core/message/229419. ( https://lists.openembedded.org/g/openembedded-core/message/229419 )
I added variables to add a deterministic entry if wanted, an offline mode based on DL_DIR, and a second .bbclass for SPDX2.2.
I can't put SPDX 2.2 and SPDX3.0 in the same class as the task scheduling is very different and a single task won't be able to handle both.
I want to add a third class for debug-source scenario but it is going to take me some time.
Do you see any other issue to solve for the current two bbclass?
[-- Attachment #2: Type: text/html, Size: 796 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: "vboudevin" <valentin.boudevin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] improve_kerne_cve_report: Add a bbclass support
Date: Thu, 15 Jan 2026 11:12:50 -0800 [thread overview]
Message-ID: <659490.1768491691095926188@lists.openembedded.org> (raw)
Message-ID: <20260115191250.YKkH2rrDY5zibRYuUUXLB-gsVGZPpsmQUmFrSOfBiFk@z> (raw)
In-Reply-To: <PA3PR07MB1072143D325ABB3729C5010D88A85A@PA3PR07MB10721.eurprd07.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
Hi Daniel,
I just pushed a V2 of my patch here: https://lists.openembedded.org/g/openembedded-core/message/229434.
I added variables to add a deterministic entry if wanted, an offline mode based on DL_DIR, and a second .bbclass for SPDX2.2.
I can't put SPDX 2.2 and SPDX3.0 in the same class as the task scheduling is very different and a single task won't be able to handle both.
I want to add a third class for debug-source scenario but it is going to take me some time.
Do you see any other issue to solve for the current two bbclass?
[-- Attachment #2: Type: text/html, Size: 685 bytes --]
next prev parent reply other threads:[~2026-01-15 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 19:42 [PATCH] improve_kerne_cve_report: Add a bbclass support ValentinBoudevin
2026-01-08 8:23 ` [OE-core] " Daniel Turull
2026-01-15 15:41 ` vboudevin [this message]
2026-01-15 19:12 ` vboudevin
[not found] ` <Groupsio.1.659490.1768491691095926188@lists.openembedded.org>
2026-01-16 9:21 ` [OE-core] " Daniel Turull
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=659490.1768491691095926188@lists.openembedded.org \
--to=valentin.boudevin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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