From: Phil Sutter <phil@nwl.cc>
To: sbezverk <sbezverk@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter <netfilter@vger.kernel.org>,
netfilter-devel <netfilter-devel@vger.kernel.org>,
netdev@vger.kernel.org, lwn@lwn.net
Subject: Re: [ANNOUNCE] nftables 0.9.4 release
Date: Thu, 2 Apr 2020 14:47:44 +0200 [thread overview]
Message-ID: <20200402124744.GY7493@orbyte.nwl.cc> (raw)
In-Reply-To: <8174B383-989D-4F9D-BDCA-3A82DE5090D2@gmail.com>
Hi Serguei,
On Thu, Apr 02, 2020 at 08:38:10AM -0400, sbezverk wrote:
> Did this commit make into 0.9.4?
>
> https://patchwork.ozlabs.org/patch/1202696/
Sadly not, as it is incomplete (anonymous LHS maps don't work due to
lack of type info). IIRC, Florian wanted to address this but I don't
know how far he got with it.
Cheers, Phil
next prev parent reply other threads:[~2020-04-02 12:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 14:31 [ANNOUNCE] nftables 0.9.4 release Pablo Neira Ayuso
2020-04-02 12:38 ` sbezverk
2020-04-02 12:47 ` Phil Sutter [this message]
2020-04-02 12:52 ` sbezverk
2020-04-02 13:32 ` Brett Mastbergen
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=20200402124744.GY7493@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=lwn@lwn.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sbezverk@gmail.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).