[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<NTZPR01MB10187B77E803325E8C88F383F837A@NTZPR01MB1018.CHNPR01.prod.partner.outlook.cn>
Date: Wed, 4 Dec 2024 15:24:38 +0000
From: EnDe Tan <ende.tan@...rfivetech.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>, "rostedt@...dmis.org"
<rostedt@...dmis.org>, "linux-rt-users@...r.kernel.org"
<linux-rt-users@...r.kernel.org>, Leyfoon Tan <leyfoon.tan@...rfivetech.com>,
"endeneer@...il.com" <endeneer@...il.com>
Subject: RE: [RT,1/1] tty/serial/sifive: Make the locking RT aware
> -----Original Message-----
> You need to state which kernel this needs to be applied to.
> The change you looking for is
> 32c694ec3efc2 ("serial: sifive: Use uart_prepare_sysrq_char() to
> handle sysrq.")
Thanks for pointing this out, I overlooked the commit in the mainline kernel.
BTW, the commit is not in v6.6.63-rt46-rebase.
Powered by blists - more mailing lists