Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Alistair Francis <alistair@alistair23.me>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libspdm: add LIBSPDM_CPE_ID_VENDOR
Date: Thu, 14 Sep 2023 22:55:15 +0200	[thread overview]
Message-ID: <20230914225515.1bd21055@windsurf> (raw)
In-Reply-To: <20230914195929.356335-1-fontaine.fabrice@gmail.com>

Hey Fabrice,

First of all, great to see you back! After several months without
contributions from you, we're glad to see you back at sending patches!

On Thu, 14 Sep 2023 21:59:29 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> cpe:2.3:a:dmtf:libspdm is a valid CPE identifier for this package:
> 
>   https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe%3A2.3%3Aa%3Admtf%3Alibspdm

In fact, I think I now prefer links such as:

  https://nvd.nist.gov/products/cpe/detail/1855641A-1A1D-4B4A-ADCD-EB3A35D35815

(which you can easily find from the previous link). Indeed this link
shows the upstream web page of the project, which is an even better
hint that the CPE identifier is indeed the right one. No need to resend
this patch nor any other you have already sent, just a suggestion for
future ones.

In any case: applied to master, thanks!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-09-14 20:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 19:59 [Buildroot] [PATCH 1/1] package/libspdm: add LIBSPDM_CPE_ID_VENDOR Fabrice Fontaine
2023-09-14 20:55 ` Thomas Petazzoni via buildroot [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=20230914225515.1bd21055@windsurf \
    --to=buildroot@buildroot.org \
    --cc=alistair@alistair23.me \
    --cc=fontaine.fabrice@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