From: "Alexis Lothoré via buildroot" <buildroot@buildroot.org>
To: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v2 2/2] support/testing: add tests for openscap
Date: Sat, 19 Sep 2026 09:36:57 +0200 [thread overview]
Message-ID: <DLJ4CYWOH1SP.2CCG0B6CZ4BID@bootlin.com> (raw)
In-Reply-To: <aq2yL_rNdxOAv-Ll@windsurf>
On Fri Sep 18, 2026 at 11:50 PM CEST, Thomas Petazzoni wrote:
> On Mon, Sep 07, 2026 at 03:47:37PM +0200, Alexis Lothoré via buildroot wrote:
>> Add basic tests for openscap, ensuring that it builds and runs a minimal
>> command with different cryptographic backends:
>> - libgcrypt
>> - libnss
>> - no crypto backend
>>
>> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
>
> Applied, after adding relevant entries in the DEVELOPERS file.
I unfortunately keep on making the same mistakes, my bad, so thanks for the fix ;)
Alexis
> Thomas
--
Alexis Lothoré, 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:[~2026-09-19 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 13:47 [Buildroot] [PATCH v2 0/2] package/openscap: fix and test build failure related to crypto Alexis Lothoré via buildroot
2026-09-07 13:47 ` [Buildroot] [PATCH v2 1/2] package: openscap: fix build failure when crypto backend is not gcrypt Alexis Lothoré via buildroot
2026-09-18 21:50 ` Thomas Petazzoni via buildroot
2026-09-07 13:47 ` [Buildroot] [PATCH v2 2/2] support/testing: add tests for openscap Alexis Lothoré via buildroot
2026-09-18 21:50 ` Thomas Petazzoni via buildroot
2026-09-19 7:36 ` Alexis Lothoré via buildroot [this message]
2026-09-25 14:43 ` Raphaël Mélotte 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=DLJ4CYWOH1SP.2CCG0B6CZ4BID@bootlin.com \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox