From: Simon Horman <horms@kernel.org>
To: Julian Anastasov <ja@ssi.bg>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
lvs-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH nf-next v3 0/4] ipvs: Cleanups for v6.4
Date: Mon, 17 Apr 2023 17:10:44 +0200 [thread overview]
Message-ID: <20230409-ipvs-cleanup-v3-0-5149ea34b0b9@kernel.org> (raw)
Hi Julian,
this series aims to clean up IPVS in several ways without
implementing any functional changes, aside from removing
some debugging output.
Patch 1/4: Update width of source for ip_vs_sync_conn_options
The operation is safe, use an annotation to describe it properly.
Patch 2/4: Consistently use array_size() in ip_vs_conn_init()
It seems better to use helpers consistently.
Patch 3/4: Remove {Enter,Leave}Function
These seem to be well past their use-by date.
Patch 4/4: Correct spelling in comments
I can't spell. But codespell helps me these days.
All changes: compile tested only!
---
Changes in v3:
- Patch 2/4: Correct division by 1024.
It was applied to the wrong variable in v2.
- Add Horatiu's Reviewed-by tag.
Changes in v2:
- Patch 1/4: Correct spelling of 'conn' in subject.
- Patch 2/4: Restore division by 1024. It was lost on v1.
---
Simon Horman (4):
ipvs: Update width of source for ip_vs_sync_conn_options
ipvs: Consistently use array_size() in ip_vs_conn_init()
ipvs: Remove {Enter,Leave}Function
ipvs: Correct spelling in comments
include/net/ip_vs.h | 32 +++++----------------
net/netfilter/ipvs/ip_vs_conn.c | 12 ++++----
net/netfilter/ipvs/ip_vs_core.c | 8 ------
net/netfilter/ipvs/ip_vs_ctl.c | 26 +----------------
net/netfilter/ipvs/ip_vs_sync.c | 7 +----
net/netfilter/ipvs/ip_vs_xmit.c | 62 ++++++-----------------------------------
6 files changed, 23 insertions(+), 124 deletions(-)
base-commit: 99676a5766412f3936c55b9d18565d248e5463ee
next reply other threads:[~2023-04-17 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 15:10 Simon Horman [this message]
2023-04-17 15:10 ` [PATCH nf-next v3 1/4] ipvs: Update width of source for ip_vs_sync_conn_options Simon Horman
2023-04-17 15:10 ` [PATCH nf-next v3 2/4] ipvs: Consistently use array_size() in ip_vs_conn_init() Simon Horman
2023-04-17 15:10 ` [PATCH nf-next v3 3/4] ipvs: Remove {Enter,Leave}Function Simon Horman
2023-04-17 15:10 ` [PATCH nf-next v3 4/4] ipvs: Correct spelling in comments Simon Horman
2023-04-17 16:59 ` [PATCH nf-next v3 0/4] ipvs: Cleanups for v6.4 Julian Anastasov
2023-04-21 23:13 ` Pablo Neira Ayuso
2023-04-22 10:14 ` Julian Anastasov
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=20230409-ipvs-cleanup-v3-0-5149ea34b0b9@kernel.org \
--to=horms@kernel.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horatiu.vultur@microchip.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=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).