From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: stable-rt <stable-rt@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v5.10-rt] rt: fix build issue in be2net
Date: Mon, 24 Mar 2025 09:32:35 +0100 [thread overview]
Message-ID: <20250324083235.BjR4MB0k@linutronix.de> (raw)
In-Reply-To: <Z9yuIpi8zjrTCkoB@uudg.org>
On 2025-03-20 21:09:06 [-0300], Luis Claudio R. Goncalves wrote:
> Sebastian, Steven, All,
>
> Should I apply this solution in a RT update right after I release
> v5.10.235-rt128 or should I backport the definition of rt locking
> primitives from a newer PREEMPT_RT patch (say v5.15-rt or v6.1-rt)?
The statement ("return spin_unlock.*") is not very common, there is just
one "user" even in later kernels.
Backporting the definition (instead of changing the driver) would be
more consistent with later trees. I'm somewhere between the definition
backport and what is less work.
The v5.4 should be also affected, right?
Sebastian
next prev parent reply other threads:[~2025-03-24 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 0:09 [PATCH v5.10-rt] rt: fix build issue in be2net Luis Claudio R. Goncalves
2025-03-24 8:32 ` Sebastian Andrzej Siewior [this message]
2025-03-24 13:37 ` Luis Claudio R. Goncalves
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=20250324083235.BjR4MB0k@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=lgoncalv@redhat.com \
--cc=rostedt@goodmis.org \
--cc=stable-rt@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.