From: Greg KH <gregkh@linuxfoundation.org>
To: Lucid Duck <lucid_duck@justthetip.ca>
Cc: sean.wang@kernel.org, nbd@nbd.name, lorenzo@kernel.org,
linux-wireless@vger.kernel.org,
linux-mediatek@lists.infradead.org, morrownr@gmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH v4] wifi: mt76: mt7921: fix txpower reporting from rate power configuration
Date: Fri, 20 Mar 2026 07:34:22 +0100 [thread overview]
Message-ID: <2026032054-backroom-nearby-53b2@gregkh> (raw)
In-Reply-To: <20260320011727.77939-1-lucid_duck@justthetip.ca>
On Thu, Mar 19, 2026 at 06:17:27PM -0700, Lucid Duck wrote:
> Note for stable backport: this patch uses mt76_tx_power_path_delta()
> which was introduced in commit 56e38675c5bd ("mt76: support power delta
> calculation for 5 TX paths"). That commit renamed the older
> mt76_tx_power_nss_delta() and is needed as a prerequisite for the
> backport to compile.
>
> For stable kernels that don't have 56e3867, a trivial substitution of
> mt76_tx_power_nss_delta for mt76_tx_power_path_delta produces identical
> results for 1-4 chain devices (the lookup tables match exactly).
>
> Reported-by: sam8641 (compile failure on 6.12.74)
This "note for stable backport" will get lost, sorry. Can you provide
working backports to stable@vger.kernel.org when this lands in Linus's
tree?
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-20 6:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 22:22 [PATCH] wifi: mt76: connac: fix txpower_cur not being updated Lucid Duck
2026-01-27 1:59 ` Nick
2026-01-27 12:21 ` Felix Fietkau
2026-01-27 16:17 ` Bitterblue Smith
2026-01-27 17:00 ` Felix Fietkau
2026-01-30 21:54 ` [PATCH v2] wifi: mt76: mt7921: fix txpower reporting Lucid Duck
2026-02-10 3:02 ` Nick
2026-02-12 2:46 ` Lucid Duck
2026-03-09 21:50 ` Lucid Duck
2026-03-12 6:38 ` Sean Wang
2026-03-17 17:30 ` [PATCH v3 0/1] wifi: mt76: mt7921: fix txpower reporting from rate power configuration Lucid Duck
2026-03-17 17:30 ` [PATCH v3 1/1] " Lucid Duck
2026-03-17 21:51 ` Lucid Duck
2026-03-19 6:00 ` Sean Wang
2026-03-19 20:38 ` [PATCH v4] " Lucid Duck
2026-03-20 1:17 ` Lucid Duck
2026-03-20 6:34 ` Greg KH [this message]
2026-03-21 8:58 ` Sean Wang
2026-01-30 21:58 ` [PATCH v2] wifi: mt76: mt7921: fix txpower reporting Lucid Duck
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=2026032054-backroom-nearby-53b2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=lucid_duck@justthetip.ca \
--cc=morrownr@gmail.com \
--cc=nbd@nbd.name \
--cc=sean.wang@kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox