Linux real-time development
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Clark Williams <clrkwllms@kernel.org>
Cc: Wen Yang <wen.yang@linux.dev>,
	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: Thu, 22 Oct 2026 11:25:36 +0200	[thread overview]
Message-ID: <20261022092536.HVMUjSuS@linutronix.de> (raw)
In-Reply-To: <atJ0axhl3AHQIDsa@demetrius>

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

  reply	other threads:[~2026-10-22  9:25 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 [this message]
2026-10-23 17:42             ` Wen Yang
2026-10-23 21:31               ` Clark Williams

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=20261022092536.HVMUjSuS@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox