From: Benjamin Robin <benjamin.robin@bootlin.com>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.18.y 0/2] netfilter: nf_tables: join hook list via splice_list_rcu() in commit phase
Date: Mon, 28 Sep 2026 10:15:43 +0200 [thread overview]
Message-ID: <y1YYJSp3Q5q9mRFyTmWbqg@bootlin.com> (raw)
In-Reply-To: <2026-09-25-daily-reply-0004-re-nf-tables-splice-list-rcu-bounce@kernel.org>
On Friday, September 25, 2026 at 8:47 PM, Sasha Levin wrote:
> > I backported an additional patch, which adds list_splice_rcu(), which is
> > required.
> >
> > Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
>
> The code looks fine on all six trees, but your Signed-off-by is missing
> from 1/2 in every series, and from 2/2 in the 6.18, 6.12 and 6.6 ones.
> The 6.6.y series also didn't go to stable@vger.kernel.org.
>
> Could you resend all six with your Signed-off-by on every patch, and with
> stable@ on the 6.6.y one?
Hello, sorry about that. I was not sure about the rule if I did not modify
the commit in any way. I should have informed myself better.
I have sent a v2 for all kernel branches.
--
Benjamin Robin, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-09-28 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 7:52 [PATCH 6.18.y 0/2] netfilter: nf_tables: join hook list via splice_list_rcu() in commit phase Benjamin Robin (Schneider Electric)
2026-09-25 7:52 ` [PATCH 6.18.y 1/2] rculist: add list_splice_rcu() for private lists Benjamin Robin (Schneider Electric)
2026-09-25 14:23 ` Greg KH
2026-09-25 14:28 ` Benjamin Robin
2026-09-25 14:36 ` Benjamin Robin
2026-09-25 14:47 ` Greg KH
2026-09-25 7:52 ` [PATCH 6.18.y 2/2] netfilter: nf_tables: join hook list via splice_list_rcu() in commit phase Benjamin Robin (Schneider Electric)
2026-09-25 14:24 ` Greg KH
2026-09-25 18:47 ` [PATCH 6.18.y 0/2] " Sasha Levin
2026-09-28 8:15 ` Benjamin Robin [this message]
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=y1YYJSp3Q5q9mRFyTmWbqg@bootlin.com \
--to=benjamin.robin@bootlin.com \
--cc=sashal@kernel.org \
--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.