From: Jakub Kicinski <kuba@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: netdev@vger.kernel.org, horms@kernel.org, pabeni@redhat.com,
edumazet@google.com, davem@davemloft.net, idosch@nvidia.com,
dsahern@kernel.org, Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [PATCH 1/3 net-next v5] ipv4: centralize devconf sysctl handling
Date: Mon, 8 Jun 2026 09:03:33 -0700 [thread overview]
Message-ID: <20260608090333.21c94721@kernel.org> (raw)
In-Reply-To: <20260607110123.5939-1-fmancera@suse.de>
On Sun, 7 Jun 2026 13:01:21 +0200 Fernando Fernandez Mancera wrote:
> The logic for handling IPv4 devconf sysctls is scattered. Notification
> and cache flushes are managed in devinet_conf_proc(), while a separate
> ipv4_doint_and_flush() function and DEVINET_SYSCTL_FLUSHING_ENTRY macro
> is used for properties that solely require a cache flush.
Hi Fernando!
Do you have the necessary iproute2 patches pushed out somewhere?
I'll pull them in the CI to make sure the test works.
next prev parent reply other threads:[~2026-06-08 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 11:01 [PATCH 1/3 net-next v5] ipv4: centralize devconf sysctl handling Fernando Fernandez Mancera
2026-06-07 11:01 ` [PATCH 2/3 net-next v5] ipv4: handle devconf post-set actions on netlink updates Fernando Fernandez Mancera
2026-06-07 11:01 ` [PATCH 3/3 net-next v5] selftests: net: add test for IPv4 devconf netlink notifications Fernando Fernandez Mancera
2026-06-08 16:03 ` Jakub Kicinski [this message]
2026-06-08 17:41 ` [PATCH 1/3 net-next v5] ipv4: centralize devconf sysctl handling Fernando Fernandez Mancera
2026-06-09 2:32 ` Jakub Kicinski
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=20260608090333.21c94721@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.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.