From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 0/2] Improving CVE reporting
Date: Mon, 21 Sep 2020 12:14:45 +0200 [thread overview]
Message-ID: <87sgbbigh6.fsf@BL-laptop> (raw)
In-Reply-To: <20200919141639.17a1a41a@windsurf.hq.k.grp>
Hello Thomas,
> Hello,
>
> On Fri, 18 Sep 2020 12:22:23 +0200
> Gregory CLEMENT <gregory.clement@bootlin.com> wrote:
>
>> Gregory CLEMENT (2):
>> support/script/pkg-stats: Manage the CVEs that need to be check
>> support/script/cve-checker: Manage the CVEs that need to be check
>
> From your previous iteration, 3 patches were still pending, but you're
> only resending 2 here.
>
> What happened with
> https://patchwork.ozlabs.org/project/buildroot/patch/20200724154356.2607639-9-gregory.clement at bootlin.com/
> ?
I thought it was already applied I get it mixed up with another patch.
I am sending a v5 with the missing patch.
Gregory
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2020-09-21 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 10:22 [Buildroot] [PATCH v4 0/2] Improving CVE reporting Gregory CLEMENT
2020-09-18 10:22 ` [Buildroot] [PATCH v4 1/2] support/script/pkg-stats: Manage the CVEs that need to be check Gregory CLEMENT
2020-09-18 10:22 ` [Buildroot] [PATCH v4 2/2] support/script/cve-checker: " Gregory CLEMENT
2020-09-19 12:16 ` [Buildroot] [PATCH v4 0/2] Improving CVE reporting Thomas Petazzoni
2020-09-21 10:14 ` Gregory CLEMENT [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=87sgbbigh6.fsf@BL-laptop \
--to=gregory.clement@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox