From: Julien Olivain <ju.o@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next 2/2] package/kexec: add KEXEC_CPE_ID_VENDOR
Date: Sun, 12 Mar 2023 22:54:17 +0100 [thread overview]
Message-ID: <c7ca2041d49a6736f92eb7b1fd51d342@free.fr> (raw)
In-Reply-To: <20230312133434.3081ee6a@windsurf>
Hi Thomas,
On 12/03/2023 13:34, Thomas Petazzoni wrote:
> On Wed, 1 Mar 2023 23:01:59 +0100
> Julien Olivain <ju.o@free.fr> wrote:
>
>> cpe:2.3:a:kexec-tools_project:kexec-tools is a valid CPE identifier
>
> But then you also need:
>
> KEXEC_CPE_ID_PRODUCT = kexec-tools
>
> indeed, by default, the value of KEXEC_CPE_ID_PRODUCT is the name of
> the Buildroot package, lower-case, so currently the value of
> KEXEC_CPE_ID_PRODUCT is "kexec", not "kexec-tools".
>
> Am I missing something here?
You are right! I indeed missed the _PRODUCT.
I'll add it and send a v2.
> You can double check this by running "make pkg-stats" on a
> configuration that has kexec enabled. In the last column of the table,
> it will tell you if the CPE ID is found in the database.
>
> Best regards,
>
> Thomas
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-12 22:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 22:01 [Buildroot] [PATCH next 1/2] package/kexec: bump to version 2.0.26 Julien Olivain
2023-03-01 22:01 ` [Buildroot] [PATCH next 2/2] package/kexec: add KEXEC_CPE_ID_VENDOR Julien Olivain
2023-03-12 12:34 ` Thomas Petazzoni via buildroot
2023-03-12 21:54 ` Julien Olivain [this message]
2023-03-12 21:59 ` [Buildroot] [PATCH v2 1/1] package/kexec: add KEXEC_CPE_ID_{PRODUCT, VENDOR} Julien Olivain
2023-03-12 22:14 ` Thomas Petazzoni via buildroot
2023-03-19 16:36 ` Peter Korsgaard
2023-03-12 12:34 ` [Buildroot] [PATCH next 1/2] package/kexec: bump to version 2.0.26 Thomas Petazzoni via buildroot
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=c7ca2041d49a6736f92eb7b1fd51d342@free.fr \
--to=ju.o@free.fr \
--cc=buildroot@buildroot.org \
--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;
as well as URLs for NNTP newsgroup(s).