public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: wen.yang@linux.dev
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.1 0/3] net: Backlog NAPI threading for PREEMPT_RT
Date: Tue, 3 Feb 2026 16:52:19 +0100	[thread overview]
Message-ID: <2026020340-preseason-matchless-e51c@gregkh> (raw)
In-Reply-To: <cover.1768754220.git.wen.yang@linux.dev>

On Mon, Jan 19, 2026 at 12:40:30AM +0800, wen.yang@linux.dev wrote:
> From: Wen Yang <wen.yang@linux.dev>
> 
> Backport three upstream commits to fix a warning on PREEMPT_RT kernels
> where raising SOFTIRQ from smp_call_functio triggers WARN_ON_ONCE()
> in do_softirq_post_smp_call_flush().

But PREEMPT_RT showed up for real in 6.12.y, NOT 6.1.y. We are reverting
PREEMPT_RT-only patches from the latest 6.6.y tree at the moment, why
are these needed here for 6.1.y at all?

confused,

greg k-h

  parent reply	other threads:[~2026-02-03 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18 16:40 [PATCH 6.1 0/3] net: Backlog NAPI threading for PREEMPT_RT wen.yang
2026-01-18 16:40 ` [PATCH 6.1 1/3] net: napi_schedule_rps() cleanup wen.yang
2026-01-18 16:40 ` [PATCH 6.1 2/3] net: Remove conditional threaded-NAPI wakeup based on task state wen.yang
2026-01-18 16:40 ` [PATCH 6.1 3/3] net: Allow to use SMP threads for backlog NAPI wen.yang
2026-02-03 15:52 ` Greg Kroah-Hartman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-18 16:15 [PATCH 6.6 0/3] net: Backlog NAPI threading for PREEMPT_RT wen.yang
2026-01-18 16:17 ` [PATCH 6.1 " wen.yang
2026-01-18 16:28 ` wen.yang

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=2026020340-preseason-matchless-e51c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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