From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Clinux=40weissschuh=2Enet=3E?=@ci.codeaurora.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, horms@verge.net.au,
ja@ssi.bg, pablo@netfilter.org, kadlec@netfilter.org,
j.granados@samsung.com, mcgrof@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvs-devel@vger.kernel.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org
Subject: Re: [PATCH net-next 0/5] net: constify ctl_table arguments of utility functions
Date: Wed, 29 May 2024 02:57:01 +0000 [thread overview]
Message-ID: <171695142181.13406.6878241525958954105.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240527-sysctl-const-handler-net-v1-0-16523767d0b2@weissschuh.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 27 May 2024 19:04:18 +0200 you wrote:
> The sysctl core is preparing to only expose instances of
> struct ctl_table as "const".
> This will also affect the ctl_table argument of sysctl handlers.
>
> As the function prototype of all sysctl handlers throughout the tree
> needs to stay consistent that change will be done in one commit.
>
> [...]
Here is the summary with links:
- [net-next,1/5] net/neighbour: constify ctl_table arguments of utility function
https://git.kernel.org/netdev/net-next/c/874aa96d78c7
- [net-next,2/5] net/ipv4/sysctl: constify ctl_table arguments of utility functions
https://git.kernel.org/netdev/net-next/c/551814313f11
- [net-next,3/5] net/ipv6/addrconf: constify ctl_table arguments of utility functions
https://git.kernel.org/netdev/net-next/c/c55eb03765f4
- [net-next,4/5] net/ipv6/ndisc: constify ctl_table arguments of utility function
https://git.kernel.org/netdev/net-next/c/7a20cd1e71d8
- [net-next,5/5] ipvs: constify ctl_table arguments of utility functions
https://git.kernel.org/netdev/net-next/c/0a9f788fdde4
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:[~2024-05-29 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 17:04 [PATCH net-next 0/5] net: constify ctl_table arguments of utility functions Thomas Weißschuh
2024-05-27 17:04 ` [PATCH net-next 1/5] net/neighbour: constify ctl_table arguments of utility function Thomas Weißschuh
2024-05-27 17:04 ` [PATCH net-next 2/5] net/ipv4/sysctl: constify ctl_table arguments of utility functions Thomas Weißschuh
2024-05-27 17:04 ` [PATCH net-next 3/5] net/ipv6/addrconf: " Thomas Weißschuh
2024-05-27 17:04 ` [PATCH net-next 4/5] net/ipv6/ndisc: constify ctl_table arguments of utility function Thomas Weißschuh
2024-05-27 17:04 ` [PATCH net-next 5/5] ipvs: constify ctl_table arguments of utility functions Thomas Weißschuh
2024-05-29 2:57 ` 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=171695142181.13406.6878241525958954105.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Thomas_Wei=C3=9Fschuh_=3Clinux=40weissschuh=2Enet=3E?=@ci.codeaurora.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@verge.net.au \
--cc=j.granados@samsung.com \
--cc=ja@ssi.bg \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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).