[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b945bd5f3d414ac5bc589d65cf439f7b@fintech.ru>
Date: Mon, 30 Jan 2023 13:27:26 +0000
From: Жандарович Никита Игоревич <n.zhandarovich@...tech.ru>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: "stable@...r.kernel.org" <stable@...r.kernel.org>,
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" <linux-wireless@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-mediatek@...ts.infradead.org"
<linux-mediatek@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Alexey Khoroshilov" <khoroshilov@...ras.ru>,
"lvc-project@...uxtesting.org" <lvc-project@...uxtesting.org>
Subject: RE: [PATCH 5.10 1/1] mt76: fix mt7615_init_tx_queues() return value
> What is the git commit id of this upstream?
>
> And I can't apply this as-is for the obvious reason it would mess up the
> changelog, how did you create this?
>
> confused,
>
> greg k-h
Commit in question is b671da33d1c5973f90f098ff66a91953691df582 upstream. I wasn't certain it makes sense to backport the whole patch as only a small portion of it pertains to the fault at question.
Would be extremely grateful for directions how to proceed from here.
somewhat embarrassed,
Nikita
Powered by blists - more mailing lists