From: Florian Westphal <fw@strlen.de>
To: Eric Woudstra <ericwouds@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v19 nf-next 5/5] netfilter: nft_chain_filter: Add bridge double vlan and pppoe
Date: Tue, 10 Mar 2026 14:26:30 +0100 [thread overview]
Message-ID: <abAcBtV9WbEIDgCt@strlen.de> (raw)
In-Reply-To: <f69a9456-5047-4044-aa8d-1bad3bd81f4b@gmail.com>
Eric Woudstra <ericwouds@gmail.com> wrote:
> I misunderstood, as Florian pointed out he is waiting for a response on
> the AI generated review.
Yes, I also try to keep patchwork somewhat up to date.
If its not listed anymore, its been dropped from my radar.
If its in new or 'under review' state, then its still on my list
and I will get to it.
> I now understand it was not forgotten at all.
Well, it was forgotten, sort of.
I depend on patchwork tracking (and on submitters checking
back when they are unsure (so this ping isn't bad)).
Would it help to add a netfilter process document to
Documentation/process/ to explain the expectations and
nf specific patch workflow?
next prev parent reply other threads:[~2026-03-10 13:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 6:53 [PATCH v19 nf-next 0/5] conntrack: bridge: add double vlan, pppoe and pppoe-in-q Eric Woudstra
2026-02-24 6:53 ` [PATCH v19 nf-next 1/5] net: pppoe: avoid zero-length arrays in struct pppoe_hdr Eric Woudstra
2026-02-24 14:15 ` Florian Westphal
2026-02-24 6:53 ` [PATCH v19 nf-next 2/5] netfilter: utils: nf_checksum(_partial) correct data!=networkheader Eric Woudstra
2026-02-24 6:53 ` [PATCH v19 nf-next 3/5] netfilter: bridge: Add conntrack double vlan and pppoe Eric Woudstra
2026-02-25 1:52 ` [v19,nf-next,3/5] " Jakub Kicinski
2026-02-24 6:53 ` [PATCH v19 nf-next 4/5] netfilter: nft_set_pktinfo_ipv4/6_validate: Add nhoff argument Eric Woudstra
2026-02-25 1:52 ` [v19,nf-next,4/5] " Jakub Kicinski
2026-02-24 6:53 ` [PATCH v19 nf-next 5/5] netfilter: nft_chain_filter: Add bridge double vlan and pppoe Eric Woudstra
2026-03-10 8:37 ` Eric Woudstra
2026-03-10 12:39 ` Florian Westphal
[not found] ` <abAOwZDmHjcLIbj1@chamomile>
[not found] ` <f69a9456-5047-4044-aa8d-1bad3bd81f4b@gmail.com>
2026-03-10 13:26 ` Florian Westphal [this message]
2026-03-10 14:45 ` Eric Woudstra
2026-03-10 15:40 ` Florian Westphal
2026-03-11 10:07 ` Pablo Neira Ayuso
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=abAcBtV9WbEIDgCt@strlen.de \
--to=fw@strlen.de \
--cc=ericwouds@gmail.com \
--cc=netfilter-devel@vger.kernel.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