From: patchwork-bot+netdevbpf@kernel.org
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: netdev@vger.kernel.org, horms@kernel.org, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, dsahern@kernel.org,
idosch@nvidia.com, davem@davemloft.net,
nicolas.dichtel@6wind.com
Subject: Re: [PATCH 1/3 net-next v6] ipv4: centralize devconf sysctl handling
Date: Sat, 13 Jun 2026 21:20:11 +0000 [thread overview]
Message-ID: <178138561113.1597380.7779221670234945181.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609204520.4670-1-fmancera@suse.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 9 Jun 2026 22:45:18 +0200 you 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.
>
> This patch refactors the sysctl handling by introducing a centralized
> helper, devinet_conf_post_set(). This new function evaluates the changed
> attribute and handles all necessary operations like triggering netlink
> notifications. It returns a boolean indicating whether a routing cache
> flush is required.
>
> [...]
Here is the summary with links:
- [1/3,net-next,v6] ipv4: centralize devconf sysctl handling
https://git.kernel.org/netdev/net-next/c/3a29b55505f3
- [2/3,net-next,v6] ipv4: handle devconf post-set actions on netlink updates
https://git.kernel.org/netdev/net-next/c/489730ec2a73
- [3/3,net-next,v6] selftests: net: add test for IPv4 devconf netlink notifications
https://git.kernel.org/netdev/net-next/c/32229484e381
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-13 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 20:45 [PATCH 1/3 net-next v6] ipv4: centralize devconf sysctl handling Fernando Fernandez Mancera
2026-06-09 20:45 ` [PATCH 2/3 net-next v6] ipv4: handle devconf post-set actions on netlink updates Fernando Fernandez Mancera
2026-06-12 12:38 ` Simon Horman
2026-06-12 16:44 ` Fernando Fernandez Mancera
2026-06-09 20:45 ` [PATCH 3/3 net-next v6] selftests: net: add test for IPv4 devconf netlink notifications Fernando Fernandez Mancera
2026-06-13 21:20 ` patchwork-bot+netdevbpf [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=178138561113.1597380.7779221670234945181.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=kuba@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox