All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, linux@slavino.sk
Subject: Re: [PATCH nft] Revert "intervals: do not merge intervals with different timeout"
Date: Thu, 17 Apr 2025 15:41:46 +0200	[thread overview]
Message-ID: <20250417134146.GA17435@breakpoint.cc> (raw)
In-Reply-To: <20250417121511.19312-1-pablo@netfilter.org>

Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> This reverts commit da0bac050c8b2588242727f9915a1ea8bc48ceb2.
> 
> This results in an error when adding an interval that overlaps an
> existing interval in the kernel, this defeats the purpose of the
> auto-merge feature.

Do we need a new nft release?  I'd like to avoid people
relying on the 'just reverted' behaviour.

  reply	other threads:[~2025-04-17 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 12:15 [PATCH nft] Revert "intervals: do not merge intervals with different timeout" Pablo Neira Ayuso
2025-04-17 13:41 ` Florian Westphal [this message]
2025-04-17 15:21   ` 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=20250417134146.GA17435@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=linux@slavino.sk \
    --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.