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
Subject: Re: [PATCH nf-next 0/4] ipvs: Cleanups for v6.4
Date: Mon, 10 Apr 2023 14:20:46 +0200 [thread overview]
Message-ID: <ZDP/Ht1Nb4iRSkI8@kernel.org> (raw)
In-Reply-To: <20230409-ipvs-cleanup-v1-0-98cdc242feb0@kernel.org>
On Mon, Apr 10, 2023 at 11:42:34AM +0200, Simon Horman wrote:
> Hi Pablo,
>
> 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_con_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!
Hi all,
Julian pointed out some minor issues which I will address in a v2.
prev parent reply other threads:[~2023-04-10 12:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 9:42 [PATCH nf-next 0/4] ipvs: Cleanups for v6.4 Simon Horman
2023-04-10 9:42 ` [PATCH nf-next 1/4] ipvs: Update width of source for ip_vs_sync_con_options Simon Horman
2023-04-10 9:42 ` [PATCH nf-next 2/4] ipvs: Consistently use array_size() in ip_vs_conn_init() Simon Horman
2023-04-10 9:42 ` [PATCH nf-next 3/4] ipvs: Remove {Enter,Leave}Function Simon Horman
2023-04-10 9:42 ` [PATCH nf-next 4/4] ipvs: Correct spelling in comments Simon Horman
2023-04-10 12:20 ` Simon Horman [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=ZDP/Ht1Nb4iRSkI8@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=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 read-only IMAP folder(s) and NNTP newsgroup(s).