From: Phil Sutter <phil@nwl.cc>
To: Florian Westphal <fw@strlen.de>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH] tests: shell: Fix ifname_based_hooks feature check
Date: Thu, 26 Jun 2025 14:29:44 +0200 [thread overview]
Message-ID: <aF09ODS5R_ZPv65v@orbyte.nwl.cc> (raw)
In-Reply-To: <aF04Q2ppk70lssKl@strlen.de>
On Thu, Jun 26, 2025 at 02:08:35PM +0200, Florian Westphal wrote:
> Phil Sutter <phil@nwl.cc> wrote:
> > Fix this by detecting whether a netdev-family chain may be added despite
> > specifying a non-existent interface to hook into. Keep the old check
> > around with a better name, although unused for now.
>
> Thanks, this makes shell tests pass on fedora 42 again, so I pushed it
> out.
Perfect, thanks!
prev parent reply other threads:[~2025-06-26 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 16:53 [nft PATCH] tests: shell: Fix ifname_based_hooks feature check Phil Sutter
2025-06-26 12:08 ` Florian Westphal
2025-06-26 12:29 ` 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=aF09ODS5R_ZPv65v@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=fw@strlen.de \
--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;
as well as URLs for NNTP newsgroup(s).