From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] libnftables: Drop symbol nft_bison_have_extended_errors
Date: Wed, 2 Sep 2026 15:16:35 +0200 [thread overview]
Message-ID: <apghs9azBbZ51hly@orbyte.nwl.cc> (raw)
In-Reply-To: <apbon9gjfoUsgSYv@chamomile>
On Tue, Sep 01, 2026 at 05:00:47PM +0200, Pablo Neira Ayuso wrote:
> On Tue, Sep 01, 2026 at 04:56:10PM +0200, Pablo Neira Ayuso wrote:
> > On Tue, Sep 01, 2026 at 11:48:52AM +0200, Phil Sutter wrote:
> > > It was merely used to indicate extended parser error support in 'nft
> > > --version' output. Not worth bumping library version just for that, so
> > > drop it again.
> > >
> > > Fixes: b315dd551dd96 ("parser_bison: Fix for bison < 3.6")
> > > Signed-off-by: Phil Sutter <phil@nwl.cc>
> >
> > Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
>
> I have applied this patch to nftables.git to prepare for the nftables
> release.
Thanks, Pablo!
prev parent reply other threads:[~2026-09-02 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 9:48 [nft PATCH] libnftables: Drop symbol nft_bison_have_extended_errors Phil Sutter
2026-09-01 14:56 ` Pablo Neira Ayuso
2026-09-01 15:00 ` Pablo Neira Ayuso
2026-09-02 13:16 ` Phil Sutter [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=apghs9azBbZ51hly@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--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