From: Matthieu Baerts <matttbe@kernel.org>
To: Breno Leitao <leitao@debian.org>,
kuba@kernel.org, horms@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com,
Andrew Lunn <andrew+netdev@lunn.ch>,
Shuah Khan <shuah@kernel.org>
Cc: thepacketgeek@gmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, davej@codemonkey.org.uk,
vlad.wing@gmail.com, max@kutsevol.com, kernel-team@meta.com,
aehkn@xenhub.one, Petr Machata <petrm@nvidia.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH net-next 1/2] net: netconsole: selftests: Change the IP subnet
Date: Mon, 28 Oct 2024 18:57:29 +0100 [thread overview]
Message-ID: <ce2892c4-f759-40ca-a188-11a83b0164b3@kernel.org> (raw)
In-Reply-To: <20241028154805.1394611-1-leitao@debian.org>
Hi Breno,
On 28/10/2024 16:48, Breno Leitao wrote:
> Use a less populated IP range to run the tests, as suggested by Petr in
> Link: https://lore.kernel.org/netdev/87ikvukv3s.fsf@nvidia.com/.
It looks like this is the same version as the one you sent on Friday,
without the modification suggested by Petr:
https://lore.kernel.org/20241025161415.238215-1-leitao@debian.org
I supposed these new patches have been sent by accident, right?
(BTW: it is often better to include a cover letter when there is more
than one patch: some CIs might not take patches sent without it.)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-10-28 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 15:48 Breno Leitao
2024-10-28 15:48 ` [PATCH net-next 2/2] net: netconsole: selftests: Add userdata validation Breno Leitao
2024-10-28 17:57 ` Matthieu Baerts [this message]
2024-10-29 9:20 ` [PATCH net-next 1/2] net: netconsole: selftests: Change the IP subnet Breno Leitao
-- strict thread matches above, loose matches on Subject: below --
2024-10-25 16:14 Breno Leitao
2024-10-25 17:01 ` Petr Machata
2024-10-25 17:35 ` Breno Leitao
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=ce2892c4-f759-40ca-a188-11a83b0164b3@kernel.org \
--to=matttbe@kernel.org \
--cc=aehkn@xenhub.one \
--cc=andrew+netdev@lunn.ch \
--cc=davej@codemonkey.org.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=max@kutsevol.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
--cc=thepacketgeek@gmail.com \
--cc=vlad.wing@gmail.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®