From: Simon Horman <horms@kernel.org>
To: Dmitry Skorodumov <skorodumov.dmitry@huawei.com>
Cc: netdev@vger.kernel.org, Xiao Liang <shaw.leon@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Guillaume Nault <gnault@redhat.com>,
Julian Vetter <julian@outer-limits.org>,
Eric Dumazet <edumazet@google.com>,
Stanislav Fomichev <sdf@fomichev.me>,
Etienne Champetier <champetier.etienne@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>
Subject: Re: [PATCH net] ipvlan: Make the addrs_lock be per port
Date: Tue, 16 Dec 2025 11:17:52 +0000 [thread overview]
Message-ID: <aUE_4PUVISMm4ycL@horms.kernel.org> (raw)
In-Reply-To: <4a0b0695-f13e-4611-a6a5-524b4967ff6e@huawei.com>
On Mon, Dec 15, 2025 at 08:00:52PM +0300, Dmitry Skorodumov wrote:
> I'm working currently on some selftests/net for ipvtap for some kind of test (test calls "ip a a/ip a d" in several threads), but I'm unsure how to proceed:
>
> This patch is supposed to be a "fix". But selftest - obviously not a fix.
>
> So, I'm unsure how to send a selftest for this.
Hi Dmitry,
I think that in cases like this - a fix coupled with a selftest for the
fixed problem - both the fix and the selftest can be included in a
patch-set targeted at net.
next prev parent reply other threads:[~2025-12-16 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 16:54 [PATCH net] ipvlan: Make the addrs_lock be per port Dmitry Skorodumov
2025-12-15 17:00 ` Dmitry Skorodumov
2025-12-16 11:17 ` Simon Horman [this message]
2025-12-23 10:13 ` Paolo Abeni
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=aUE_4PUVISMm4ycL@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=champetier.etienne@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=julian@outer-limits.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shaw.leon@gmail.com \
--cc=skorodumov.dmitry@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.