From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Skorodumov <dskr99@gmail.com>
Cc: netdev@vger.kernel.org, Dmitry Skorodumov <skorodumov.dmitry@huawei.com>
Subject: Re: [PATCH net 0/3] ipvlan: Deduplicate ipv4/ipv6 addr_validator_event code
Date: Tue, 20 Jan 2026 10:59:09 -0800 [thread overview]
Message-ID: <20260120105909.4e52de08@kernel.org> (raw)
In-Reply-To: <20260120161852.639238-1-skorodumov.dmitry@huawei.com>
On Tue, 20 Jan 2026 19:18:33 +0300 Dmitry Skorodumov wrote:
> This is a bit stylish patches: The code to handle ipv4 and ipv6
> address change are exactly the same. We don't need separate
> functions for them. Just look whether we are called
> with ipvlan_addr4_notifier_block or with ipvlan_addr6_notifier_block
[PATCH net] is for fixes, please use [PATCH net-next] for cleanups.
If these patches depend on your locking fix you'll need to wait
with reposting until the fix appears in net-next (Thu afternoon).
--
pw-bot: cr
next prev parent reply other threads:[~2026-01-20 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 16:18 [PATCH net 0/3] ipvlan: Deduplicate ipv4/ipv6 addr_validator_event code Dmitry Skorodumov
2026-01-20 16:18 ` [PATCH net 1/3] ipvlan: const-specifier for functions that use iaddr Dmitry Skorodumov
2026-01-20 16:18 ` [PATCH net 2/3] ipvlan: Common code from v6/v4 validator_event Dmitry Skorodumov
2026-01-21 15:33 ` kernel test robot
2026-01-20 16:18 ` [PATCH net 3/3] ipvlan: common code to handle ipv6/ipv4 address events Dmitry Skorodumov
2026-01-22 3:58 ` kernel test robot
2026-01-20 18:59 ` Jakub Kicinski [this message]
2026-01-23 17:06 ` [PATCH net 0/3] ipvlan: Deduplicate ipv4/ipv6 addr_validator_event code Dmitry Skorodumov
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=20260120105909.4e52de08@kernel.org \
--to=kuba@kernel.org \
--cc=dskr99@gmail.com \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox