From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Thomas Perale <thomas.perale@mind.be>
Cc: buildroot@buildroot.org, "Jérôme Pouiller" <jezz@sysmic.org>,
"Sergio Prado" <sergio.prado@e-labworks.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/strongswan: fix build w/ wolfssl 5.9.2
Date: Sat, 04 Jul 2026 16:42:48 +0200 [thread overview]
Message-ID: <1f84da0f5bc76ceb14f8ed8996813f87@free.fr> (raw)
In-Reply-To: <20260630212717.604030-1-thomas.perale@mind.be>
On 30/06/2026 23:27, Thomas Perale via buildroot wrote:
> The 'mlkem.h' header is no longer present in wolfssl v5.9.2 [1] and the
> content was merged in the 'wc_mlkem.h' header.
>
> [1]
> https://github.com/wolfSSL/wolfssl/commit/7a2cf5b655541013ed8c93ecc9f598146abf2916
>
> Signed-off-by: Thomas Perale <thomas.perale@mind.be>
Series applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-07-04 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 21:27 [Buildroot] [PATCH 1/2] package/strongswan: fix build w/ wolfssl 5.9.2 Thomas Perale via buildroot
2026-06-30 21:27 ` [Buildroot] [PATCH 2/2] package/wolfssl: security bump to v5.9.2 Thomas Perale via buildroot
2026-07-04 14:42 ` Julien Olivain 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=1f84da0f5bc76ceb14f8ed8996813f87@free.fr \
--to=buildroot@buildroot.org \
--cc=jezz@sysmic.org \
--cc=ju.o@free.fr \
--cc=sergio.prado@e-labworks.com \
--cc=thomas.perale@mind.be \
/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