From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 01/15] package/iwd: add IWD_CPE_ID_VENDOR and IWD_CPE_ID_NAME
Date: Thu, 21 Jan 2021 22:04:24 +0100 [thread overview]
Message-ID: <20210121220424.3d8157b2@windsurf.home> (raw)
In-Reply-To: <20210121133639.7332-1-heiko.thiery@gmail.com>
On Thu, 21 Jan 2021 14:36:25 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:
> cpe:2.3:a:intel:inet_wireless_daemon is a valid CPE identifier for this package:
>
> https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=iwd
>
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> ---
> package/iwd/iwd.mk | 2 ++
> 1 file changed, 2 insertions(+)
I've applied the entire series. However, your series was supposed to
have 15 patches, but the PATCH 15/15 never made it to the mailing list.
Is this expected ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-21 21:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 13:36 [Buildroot] [PATCH 01/15] package/iwd: add IWD_CPE_ID_VENDOR and IWD_CPE_ID_NAME Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 02/15] package/alsa-lib: add ALSA_LIB_CPE_ID_VENDOR Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 03/15] package/angularjs: add ANGULARJS_CPE_ID_VENDOR and ANGULARJS_CPE_ID_NAME Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 04/15] package/rauc: add RAUC_CPE_ID_VENDOR Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 05/15] package/apache: add APACHE_CPE_ID_VENDOR and APACHE_CPE_ID_NAME Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 06/15] package/libssh: add LIBSSH_CPE_ID_VENDOR Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 07/15] package/cifs-utils: add CIFS_UTILS_CPE_ID_VENDOR Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 08/15] package/samba4: add SAMBA4_CPE_ID_VENDOR and SAMBA4_CPE_ID_NAME Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 09/15] package/cjson: set CJSON_CPE_ID_VALID Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 10/15] package/jansson: add JANSSON_CPE_ID_VALID Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 11/15] package/wireshark: add WIRESHARK_CPE_ID_VENDOR Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 12/15] package/aircrack-ng: add AIRCRACK_NG_CPE_ID_VENDOR Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 13/15] package/apparmor: add APPARMOR_CPE_ID_VENDOR Heiko Thiery
2021-01-21 13:36 ` [Buildroot] [PATCH 14/15] package/libjpeg: add LIBJPEG_CPE_ID_VENDOR Heiko Thiery
2021-01-21 21:04 ` Thomas Petazzoni [this message]
2021-01-22 7:11 ` [Buildroot] [PATCH 01/15] package/iwd: add IWD_CPE_ID_VENDOR and IWD_CPE_ID_NAME Heiko Thiery
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=20210121220424.3d8157b2@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.