From: Jeremy Sowden <jeremy@azazel.net>
To: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nf-next 0/3] NF NAT deduplication refactoring
Date: Wed, 15 Mar 2023 21:49:25 +0000 [thread overview]
Message-ID: <20230315214925.GA4331@celephais.dreamlands> (raw)
In-Reply-To: <20230315214735.236444-1-jeremy@azazel.net>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
On 2023-03-15, at 21:47:32 +0000, Jeremy Sowden wrote:
> These three patches perform refactoring in NF NAT modules to remove
> duplicate code.
Whoops! Sent v1 out again by default.
J.
> Jeremy Sowden (3):
> netfilter: nf_nat_redirect: use `struct nf_nat_range2` in ipv4 API
> netfilter: nft_masq: deduplicate eval call-backs
> netfilter: nft_redir: deduplicate eval call-backs
>
> include/net/netfilter/nf_nat_redirect.h | 3 +-
> net/netfilter/nf_nat_redirect.c | 58 ++++++++---------
> net/netfilter/nft_masq.c | 75 +++++++++-------------
> net/netfilter/nft_redir.c | 84 +++++++++----------------
> net/netfilter/xt_REDIRECT.c | 10 ++-
> 5 files changed, 96 insertions(+), 134 deletions(-)
>
> --
> 2.39.2
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-15 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 21:47 [PATCH nf-next 0/3] NF NAT deduplication refactoring Jeremy Sowden
2023-03-15 21:47 ` [PATCH nf-next 1/3] netfilter: nf_nat_redirect: use `struct nf_nat_range2` in ipv4 API Jeremy Sowden
2023-03-15 21:47 ` [PATCH nf-next 2/3] netfilter: nft_masq: deduplicate eval call-backs Jeremy Sowden
2023-03-15 21:47 ` [PATCH nf-next 3/3] netfilter: nft_redir: " Jeremy Sowden
2023-03-15 21:49 ` Jeremy Sowden [this message]
2023-03-15 21:50 ` [PATCH nf-next 0/3] NF NAT deduplication refactoring Jeremy Sowden
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 13:46 Jeremy Sowden
2023-03-14 10:52 ` Pablo Neira Ayuso
2023-03-15 10:25 ` Pablo Neira Ayuso
2023-03-15 10:59 ` Jeremy Sowden
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=20230315214925.GA4331@celephais.dreamlands \
--to=jeremy@azazel.net \
--cc=netfilter-devel@vger.kernel.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).