From: Florian Westphal <fw@strlen.de>
To: Antonio Ojea <aojea@google.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v2 1/2] netfilter: nf_queue: limit the hook drop flush to the unregistered hook point
Date: Fri, 16 Oct 2026 16:13:00 +0200 [thread overview]
Message-ID: <atIw7CGcwLaPzAWh@strlen.de> (raw)
In-Reply-To: <20261016133304.1755951-1-aojea@google.com>
Antonio Ojea <aojea@google.com> wrote:
> Gentle ping. v2 addresses Florian's feedback on v1: rebased on nf-next
> and the nf_queue_nf_hook_drop() call in nft_ct.c converted as well.
>
> I rebased and retested the series today on nf-next main (a5e7d8e446af):
> it applies cleanly, builds, and nft_queue.sh passes, including the new
> test_hook_drop_scope.
I have no more feedback, LGTM.
prev parent reply other threads:[~2026-10-16 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 18:58 [PATCH nf-next v2 1/2] netfilter: nf_queue: limit the hook drop flush to the unregistered hook point Antonio Ojea
2026-09-28 18:58 ` [PATCH nf-next v2 2/2] selftests: netfilter: nft_queue: check the scope of the hook drop flush Antonio Ojea
2026-10-16 13:33 ` [PATCH nf-next v2 1/2] netfilter: nf_queue: limit the hook drop flush to the unregistered hook point Antonio Ojea
2026-10-16 14:13 ` Florian Westphal [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=atIw7CGcwLaPzAWh@strlen.de \
--to=fw@strlen.de \
--cc=aojea@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.