All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Bjørn Damstedt Rasmussen" <contact@bearware.dk>
Cc: buildroot@buildroot.org, Tudor Holton <buildroot@tudorholton.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/setserial: CPE ID for setserial
Date: Sat, 3 Oct 2026 19:50:55 +0200	[thread overview]
Message-ID: <asFAfC_1z5daFTsk@windsurf> (raw)
In-Reply-To: <20261003173657.1235590-1-contact@bearware.dk>

On Sat, Oct 03, 2026 at 07:36:56PM +0200, Bjørn Damstedt Rasmussen wrote:
> This is a valid CPE ID:
> https://nvd.nist.gov/products/cpe/search/results?keyword=cpe:2.3:a:setserial_project:setserial:2.17:*
> 
> Signed-off-by: Bjørn Damstedt Rasmussen <contact@bearware.dk>

Applied to master, thanks!

Best regards,

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

  parent reply	other threads:[~2026-10-03 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 17:36 [Buildroot] [PATCH 1/2] package/setserial: CPE ID for setserial Bjørn Damstedt Rasmussen
2026-10-03 17:36 ` [Buildroot] [PATCH 2/2] package/openjdk: CPE ID for openjdk Bjørn Damstedt Rasmussen
2026-10-03 17:52   ` Thomas Petazzoni via buildroot
2026-10-10  9:24   ` Thomas Perale via buildroot
2026-10-03 17:50 ` Thomas Petazzoni via buildroot [this message]
2026-10-10  9:24 ` [Buildroot] [PATCH 1/2] package/setserial: CPE ID for setserial Thomas Perale via buildroot
  -- strict thread matches above, loose matches on Subject: below --
2026-10-02 20:29 Bjørn Damstedt Rasmussen
2026-10-03 13:16 ` 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=asFAfC_1z5daFTsk@windsurf \
    --to=buildroot@buildroot.org \
    --cc=buildroot@tudorholton.com \
    --cc=contact@bearware.dk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.