From: Stefano Brivio <sbrivio@redhat.com>
To: Mike Dillinger <miked@softtalker.com>
Cc: Phil Sutter <phil@nwl.cc>,
Pablo Neira Ayuso <pablo@netfilter.org>,
stable@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf] nft_set_rbtree: Don't account for expired elements on insertion
Date: Thu, 4 Jun 2020 20:40:03 +0200 [thread overview]
Message-ID: <20200604204003.2b07d03a@redhat.com> (raw)
In-Reply-To: <79640a97-b164-42c4-cc24-2be1c2265e44@softtalker.com>
Mike,
On Thu, 4 Jun 2020 11:16:09 -0700
Mike Dillinger <miked@softtalker.com> wrote:
> [...]
>
> Hello All,
>
> Is there any way I can track this change so I know what kernel
> version to expect it in? Pardon my ignorance, but I'm new to Linux
> kernel changes. I have familiarity with change requests, so if I
> can follow this on GitHub or some other tracking system, that would
> be great.
Pablo, the maintainer, will answer to the original patch email once
(and if) it gets applied to the netfilter (nf.git) tree. For that part,
you can also track it here:
http://patchwork.ozlabs.org/project/netfilter-devel/list/
That should be applied to the main tree, though, before the stable team
picks it, there are several ways to track that... but you're using
Debian kernels, so I guess you're rather interested in:
https://tracker.debian.org/pkg/linux
https://tracker.debian.org/pkg/linux/rss
Changelog links are available from there too.
--
Stefano
next prev parent reply other threads:[~2020-06-04 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 23:50 [PATCH nf] nft_set_rbtree: Don't account for expired elements on insertion Stefano Brivio
2020-06-03 15:35 ` Phil Sutter
2020-06-04 18:16 ` Mike Dillinger
2020-06-04 18:40 ` Stefano Brivio [this message]
2020-06-08 18:41 ` 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=20200604204003.2b07d03a@redhat.com \
--to=sbrivio@redhat.com \
--cc=miked@softtalker.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=stable@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 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.