From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Thomas Haller <thaller@redhat.com>
Cc: NetFilter <netfilter-devel@vger.kernel.org>
Subject: Re: [nft PATCH v3 0/3] src: use reentrant getprotobyname_r()/getprotobynumber_r()/getservbyport_r()
Date: Sun, 20 Aug 2023 22:35:56 +0200 [thread overview]
Message-ID: <ZOJ5LMyDVJL7hkMf@calendula> (raw)
In-Reply-To: <bb3935579c7492373e76f8e71f4a739bcb7fcda4.camel@redhat.com>
On Fri, Aug 18, 2023 at 07:39:31PM +0200, Thomas Haller wrote:
> On Fri, 2023-08-18 at 18:12 +0200, Pablo Neira Ayuso wrote:
> > On Fri, Aug 18, 2023 at 04:08:18PM +0200, Thomas Haller wrote:
> > > Changes since version 2:
> > >
> > > - split the patch.
> > >
> > > - add and use defines NFT_PROTONAME_MAXSIZE, NFT_SERVNAME_MAXSIZE,
> > > NETDB_BUFSIZE.
> > >
> > > - add new GPL2+ source file as a place for the wrapper functions.
> >
> > Series LGTM. I would just collapse patch 1 and 2, I can do that
> > before
> > applying if you like. Or you send v4 as you prefer.
>
> Hi Pablo,
>
> if you are OK with applying it (and mangling it first), please go
> ahead.
Applied, thanks.
prev parent reply other threads:[~2023-08-20 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 14:08 [nft PATCH v3 0/3] src: use reentrant getprotobyname_r()/getprotobynumber_r()/getservbyport_r() Thomas Haller
2023-08-18 14:08 ` [nft PATCH v3 1/3] nftutils: add new internal file for general utilities Thomas Haller
2023-08-18 14:08 ` [nft PATCH v3 2/3] nftutils: add wrappers for getprotoby{name,number}_r(), getservbyport_r() Thomas Haller
2023-08-18 14:08 ` [nft PATCH v3 3/3] src: use " Thomas Haller
2023-08-18 16:12 ` [nft PATCH v3 0/3] src: use reentrant getprotobyname_r()/getprotobynumber_r()/getservbyport_r() Pablo Neira Ayuso
2023-08-18 17:39 ` Thomas Haller
2023-08-20 20:35 ` Pablo Neira Ayuso [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=ZOJ5LMyDVJL7hkMf@calendula \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=thaller@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;
as well as URLs for NNTP newsgroup(s).