From: Clark Williams <clrkwllms@kernel.org>
To: Wen Yang <wen.yang@linux.dev>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v6.1-rt 00/15] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush
Date: Fri, 23 Oct 2026 16:31:17 -0500 [thread overview]
Message-ID: <atvSJV_L6wHpYLGu@demetrius> (raw)
In-Reply-To: <058f0fd4-ed91-4e9b-84db-90e0a3aa5d19@linux.dev>
On Sat, Oct 24, 2026 at 01:42:22AM +0800, Wen Yang wrote:
>
>
> On 10/22/26 17:25, Sebastian Andrzej Siewior wrote:
> > On 2026-10-16 14:00:59 [-0500], Clark Williams wrote:
> > > Perfect. I expect you'll have a small series for v6.6-rt and then a
> > > pretty large one for v6.1-rt.
> > >
> > > Thanks Wen, I'll be ready to apply/test when you send it.
> >
> > "[PATCH 03/15] net: napi_schedule_rps() cleanup" has
> >
> > | commit 8fcb76b934daff12cde76adeab3d502eeb0734b1 upstream.
> >
> > in the middle of the commit message.
> >
> > "[PATCH 14/15] net: Allow to use SMP threads for backlog NAPI." has only
> > context related changes.
> >
> > I don't see any SMP-function calls with the series applied. This looks
> > complete to me.
> >
> > > Clark
> >
> > Sebastian
>
> Hi Sebastian, hi Clark,
>
> Thanks for checking and confirming the RPS coverage.
>
> Clark, would you mind moving the upstream commit reference in patch 03
> to the beginning of the commit message when applying the series? This
> would be a message-only correction; the code is unchanged.
>
> I'm happy to resend if you would prefer an updated series.
>
Hi Wen,
Yes, Please resend an updated series with the reference(s) the way you want
them. I'll pull them in, push up up to -next with -rc2 (just to make sure
I didn't miss anything) and then go ahead and release it.
Clark
--
The United States Coast Guard
Ruining Natural Selection since 1790
prev parent reply other threads:[~2026-10-23 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1791912669.git.wen.yang@linux.dev>
[not found] ` <20261014150853.f8I2fNx0@linutronix.de>
2026-10-14 15:11 ` [PATCH v6.1-rt 00/15] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush Sebastian Andrzej Siewior
[not found] ` <atDWZDywit4ilzJ8@demetrius>
2026-10-15 13:38 ` Sebastian Andrzej Siewior
2026-10-16 18:16 ` Wen Yang
2026-10-16 19:00 ` Clark Williams
2026-10-22 9:25 ` Sebastian Andrzej Siewior
2026-10-23 17:42 ` Wen Yang
2026-10-23 21:31 ` Clark Williams [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=atvSJV_L6wHpYLGu@demetrius \
--to=clrkwllms@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=wen.yang@linux.dev \
/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.