[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230130123655.86339-1-n.zhandarovich@fintech.ru>
Date: Mon, 30 Jan 2023 04:36:54 -0800
From: Nikita Zhandarovich <n.zhandarovich@...tech.ru>
To: <stable@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Nikita Zhandarovich <n.zhandarovich@...tech.ru>,
Felix Fietkau <nbd@....name>,
Lorenzo Bianconi <lorenzo.bianconi83@...il.com>,
Ryder Lee <ryder.lee@...iatek.com>,
Kalle Valo <kvalo@...eaurora.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
<linux-wireless@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-mediatek@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
"Alexey Khoroshilov" <khoroshilov@...ras.ru>,
<lvc-project@...uxtesting.org>
Subject: [PATCH 5.10 0/1] mt76: fix mt7615_init_tx_queues() return value
Fix mt7615_init_tx_queues() so that it returns result value of final call
to mt7615_init_tx_queue() instead of default 0. Otherwise, failure in
mt7615_init_tx_queue() is not tracked by the parent function. The patch
can be cleanly applied to the 5.10 branch.
This issue is addressed in b671da33d1c5 upstream. I decided to refrain
from backporting it whole for now.
Powered by blists - more mailing lists