From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Thomas Haller <thaller@redhat.com>
Cc: NetFilter <netfilter-devel@vger.kernel.org>
Subject: Re: [nft PATCH v5 0/6] add input flags and "no-dns"/"json" flags
Date: Thu, 24 Aug 2023 09:03:16 +0200 [thread overview]
Message-ID: <ZOcAtG++Pcxdst9x@calendula> (raw)
In-Reply-To: <20230818094335.535872-1-thaller@redhat.com>
On Fri, Aug 18, 2023 at 11:40:35AM +0200, Thomas Haller wrote:
> Changes since v4:
>
> - rename python API {set,get}_input() to {set,get}_input_flags() and
> update commit message. Other 5 out of 6 patches are unchanged (except
> adding Reviewed-by tag from Phil).
>
> Changes since v3:
>
> - set-input() now returns the old value (both for Python and C API)
> - python: API follows the style of existing set_debug()/get_debug()
> methods.
> - nft_input_no_dns()/nft_input_json() helper functions added and used.
> - python: new patch to better handle exception while creating Nftables
> instance.
Series applied, thanks.
prev parent reply other threads:[~2023-08-24 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 9:40 [nft PATCH v5 0/6] add input flags and "no-dns"/"json" flags Thomas Haller
2023-08-18 9:40 ` [nft PATCH v5 1/6] src: add input flags for nft_ctx Thomas Haller
2023-08-18 9:40 ` [nft PATCH v5 2/6] src: add input flag NFT_CTX_INPUT_NO_DNS to avoid blocking Thomas Haller
2023-08-18 9:40 ` [nft PATCH v5 3/6] src: add input flag NFT_CTX_INPUT_JSON to enable JSON parsing Thomas Haller
2023-08-18 9:40 ` [nft PATCH v5 4/6] py: fix exception during cleanup of half-initialized Nftables Thomas Haller
2023-08-18 9:40 ` [nft PATCH v5 5/6] py: extract flags helper functions for set_debug()/get_debug() Thomas Haller
2023-08-18 9:40 ` [nft PATCH v5 6/6] py: add Nftables.{get,set}_input_flags() API Thomas Haller
2023-08-24 7:03 ` 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=ZOcAtG++Pcxdst9x@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).