From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: buildroot@buildroot.org, Bernd Kuhls <bernd@kuhls.net>,
nicolas.carrier@nav-timing.safrangroup.com
Subject: Re: [Buildroot] [PATCH RESEND 2/2] support/testing: add basic runtime test for libldns/drill
Date: Fri, 17 Oct 2025 08:46:57 +0200 [thread overview]
Message-ID: <20251017084657.21b8d34b@windsurf> (raw)
In-Reply-To: <20251016-libldns_drill-v1-2-21bfa8c53896@bootlin.com>
Hello,
On Thu, 16 Oct 2025 17:27:03 +0200
Alexis Lothoré <alexis.lothore@bootlin.com> wrote:
> Add a simple test ensuring that
> - libldns is correctly built and installed
> - drill is correctly built and installed
> - drill is able to execute on the target
>
> Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-10-17 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 15:27 [Buildroot] [PATCH RESEND 0/2] package/libldns: allow to build drill Alexis Lothoré via buildroot
2025-10-16 15:27 ` [Buildroot] [PATCH RESEND 1/2] package/libldns: add an option to build and install drill Alexis Lothoré via buildroot
2025-10-17 6:46 ` Thomas Petazzoni via buildroot
2025-10-17 7:10 ` Alexis Lothoré via buildroot
2025-10-16 15:27 ` [Buildroot] [PATCH RESEND 2/2] support/testing: add basic runtime test for libldns/drill Alexis Lothoré via buildroot
2025-10-17 6:46 ` Thomas Petazzoni 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=20251017084657.21b8d34b@windsurf \
--to=buildroot@buildroot.org \
--cc=alexis.lothore@bootlin.com \
--cc=bernd@kuhls.net \
--cc=nicolas.carrier@nav-timing.safrangroup.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