From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Petr Machata <petrm@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, David Ahern <dsahern@gmail.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Ido Schimmel <idosch@nvidia.com>,
mlxsw@nvidia.com, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2 14/14] selftests: forwarding: Add a test for verifying VXLAN MC underlay
Date: Mon, 16 Jun 2025 13:55:09 -0700 [thread overview]
Message-ID: <20250616135509.255a1871@kernel.org> (raw)
In-Reply-To: <be7149b5-0286-4b39-b6ce-809618354b13@kernel.org>
On Mon, 16 Jun 2025 22:40:49 +0200 Matthieu Baerts wrote:
> > Good point. The question then is whether to put it to forwarding/ or
> > directly net/, which is has seen more use of lib.sh and therefore the
> > same sort of coding style. I'll experiment with it and should be able to
> > send it later in the week. I don't want to add it to the MC patchset.
>
> Since Jakub disabled SC2317 in NIPA [1], then I guess we can put this
> .shellcheckrc file in net/, no?
And drivers/net while at it, if you don't mind.
prev parent reply other threads:[~2025-06-16 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1749757582.git.petrm@nvidia.com>
2025-06-12 20:10 ` [PATCH net-next v2 11/14] selftests: forwarding: lib: Move smcrouted helpers here Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 12/14] selftests: net: lib: Add ip_link_has_flag() Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 13/14] selftests: forwarding: adf_mcd_start(): Allow configuring custom interfaces Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 14/14] selftests: forwarding: Add a test for verifying VXLAN MC underlay Petr Machata
2025-06-13 16:57 ` Jakub Kicinski
2025-06-13 17:28 ` Matthieu Baerts
2025-06-16 15:06 ` Petr Machata
2025-06-16 16:18 ` Matthieu Baerts
2025-06-16 17:52 ` Jakub Kicinski
2025-06-16 19:53 ` Petr Machata
2025-06-16 20:40 ` Matthieu Baerts
2025-06-16 20:55 ` 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=20250616135509.255a1871@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=shuah@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).