From: Jakub Kicinski <kuba@kernel.org>
To: "Maxime Chevallier (Netdev Foundation)" <maxime.chevallier@bootlin.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Donald Hunter <donald.hunter@gmail.com>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
matttbe@kernel.org, Stanislav Fomichev <sdf@fomichev.me>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] selftests: drv-net: Allow cross-compiling the hardware tests
Date: Tue, 8 Sep 2026 17:30:31 -0700 [thread overview]
Message-ID: <20260908173031.738a17fb@kernel.org> (raw)
In-Reply-To: <20260907161438.755125-1-maxime.chevallier@bootlin.com>
On Mon, 7 Sep 2026 18:14:34 +0200 Maxime Chevallier (Netdev
Foundation) wrote:
> Changes come from Sashiko reviews, that detected some Makefile inclusion
> ordering issues, a stray 'Q = @' in the ynl makefiles to have proper
> verbosity support, and some commit log rewording.
Looks good enough, if it works for you.
If we see a lot of follow ups and variance in the env people want
to support we'll have to add some kind of a build test env on QEMU.
prev parent reply other threads:[~2026-09-09 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 16:14 Maxime Chevallier (Netdev Foundation)
2026-09-07 16:14 ` [PATCH net-next v3 1/2] tools: ynl: Allow cross-compiling ynl and associated tools Maxime Chevallier (Netdev Foundation)
2026-09-08 16:17 ` netdev-bot+sashiko
2026-09-09 1:11 ` Bobby Eshleman
2026-09-07 16:14 ` [PATCH net-next v3 2/2] selftests: drv-net: Use cross-compilation environment for the io_uring check Maxime Chevallier (Netdev Foundation)
2026-09-08 16:17 ` netdev-bot+sashiko
2026-09-09 0:30 ` [PATCH net-next v3 0/2] selftests: drv-net: Allow cross-compiling the hardware tests patchwork-bot+netdevbpf
2026-09-09 0:30 ` Jakub Kicinski [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=20260908173031.738a17fb@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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
all inboxes | Powered by JetHome®