From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Mukul Sikka <mukul.sikka@broadcom.com>,
Keerthana K <keerthana.kalyanasundaram@broadcom.com>,
Stefano Brivio <sbrivio@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Brennan Lamoreaux <brennan.lamoreaux@broadcom.com>,
Bin Lan <lanbincn@139.com>, XiaoHua Wang <561399680@139.com>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Karl Mehltretter <kmehltretter@gmail.com>
Subject: Re: [PATCH 6.1.y 6.6.y] netfilter: nft_set_pipapo: restore cloned mapping table memcg accounting
Date: Wed, 2 Sep 2026 18:14:13 -0400 [thread overview]
Message-ID: <20260902-daily-reply-0014-pipapo-fixes-tag-ack@kernel.org> (raw)
In-Reply-To: <20260831194905.45045-1-kmehltretter@gmail.com>
> Fixes: a4983e89e3b1 ("netfilter: nft_set_pipapo: do not rely on ZERO_SIZE_PTR")
> Fixes: 32bad10de347 ("netfilter: nft_set_pipapo: do not rely on ZERO_SIZE_PTR")
>
> This two Fixes: tag do not make any sense to me.
> The two Fixes tags are for the two stable branches:
>
> - a4983e89e3b1 is the 6.1.y backport
> - 32bad10de347 is the 6.6.y backport
>
> I am not sure what the usual preference is here: one common patch with
> both Fixes tags, or separate patches for each tree. Which do you prefer?
Whatever Pablo prefers :)
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-02 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 19:49 Karl Mehltretter
2026-08-31 22:15 ` Pablo Neira Ayuso
2026-08-31 23:15 ` Karl Mehltretter
2026-09-02 22:14 ` Sasha Levin [this message]
2026-09-02 23:14 ` Pablo Neira Ayuso
2026-09-03 0:01 ` Karl Mehltretter
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=20260902-daily-reply-0014-pipapo-fixes-tag-ack@kernel.org \
--to=sashal@kernel.org \
--cc=561399680@139.com \
--cc=brennan.lamoreaux@broadcom.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=keerthana.kalyanasundaram@broadcom.com \
--cc=kmehltretter@gmail.com \
--cc=kuba@kernel.org \
--cc=lanbincn@139.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mukul.sikka@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
--cc=sbrivio@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®