From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Daniel Lang <dalang@gmx.at>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH] package/exim: drop stale CVE-2022-3559
Date: Mon, 2 Jun 2025 23:23:28 +0200 [thread overview]
Message-ID: <20250602232328.1088c65e@booty> (raw)
In-Reply-To: <20250602184049.933226-1-dalang@gmx.at>
On Mon, 2 Jun 2025 20:40:48 +0200
Daniel Lang <dalang@gmx.at> wrote:
> The CVE database was updated and includes the additional "up to
> (including) 4.97" version information.
>
> Signed-off-by: Daniel Lang <dalang@gmx.at>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-06-02 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 18:40 [Buildroot] [PATCH] package/exim: drop stale CVE-2022-3559 Daniel Lang via buildroot
2025-06-02 21:23 ` Luca Ceresoli via buildroot [this message]
2025-06-03 20:27 ` Peter Korsgaard
2025-06-12 20:07 ` Arnout Vandecappelle 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=20250602232328.1088c65e@booty \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=dalang@gmx.at \
--cc=luca.ceresoli@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