All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Julius Bairaktaris <julius@bairaktaris.de>
Cc: netfilter-devel@vger.kernel.org, ericwouds@gmail.com,
	razor@blackwall.org
Subject: Re: [PATCH nf-next] netfilter: flowtable: teardown flow reaching bridge port on fdb updates
Date: Thu, 15 Oct 2026 00:19:23 +0200	[thread overview]
Message-ID: <as__66RGd9zNVrcd@chamomile> (raw)
In-Reply-To: <CAC1t37+TzhPP1Q1HZVQUw=vLUxsHwpmyFWHyQWyGyOJnvSUKBQ@mail.gmail.com>

On Wed, Oct 14, 2026 at 10:00:47PM +0000, Julius Bairaktaris wrote:
[...] 
> Your version is smaller in the tuple and cheaper in the gc, though.
> I can send a v7 that takes the fdb lookup from yours and keeps the
> fixes above, if that works for you.

Please, go ahead, let's see how v7 looks like.

  reply	other threads:[~2026-10-14 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 21:02 [PATCH nf-next] netfilter: flowtable: teardown flow reaching bridge port on fdb updates Pablo Neira Ayuso
2026-10-14 22:00 ` Julius Bairaktaris
2026-10-14 22:19   ` Pablo Neira Ayuso [this message]
2026-10-15 11:56 ` kernel test robot
2026-10-15 12:07 ` kernel test robot

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=as__66RGd9zNVrcd@chamomile \
    --to=pablo@netfilter.org \
    --cc=ericwouds@gmail.com \
    --cc=julius@bairaktaris.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=razor@blackwall.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.