linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: jelonek.jonas@gmail.com, johannes.berg@intel.com,
	lorenzo.bianconi83@gmail.com, sean.wang@mediatek.com,
	Linux List Kernel Mailing <linux-wireless@vger.kernel.org>,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: After commit 44fa75f207d8a106bc75e6230db61e961fdbf8a8 Wi-Fi (mt7921e) speed significantly decreased
Date: Mon, 26 Sep 2022 15:27:06 +0500	[thread overview]
Message-ID: <CABXGCsPg4mEe0RfJeXCGQ_WatbHgGi16Xw9DFKxPLV8QNi777A@mail.gmail.com> (raw)
In-Reply-To: <4e7992e2-c635-e571-faa3-08fd9ee5c975@leemhuis.info>

On Mon, Sep 26, 2022 at 9:38 AM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> FWIW, there is a patch under discussion fixing a problem found in that
> commit:
>
> https://lore.kernel.org/all/20220829144147.484787-2-jelonek.jonas@gmail.com/
>
> To quote the first para:
>
> ```
> This patch modifies the annotation of supported tx-power levels for a
> wifi device in ieee80211_hw. This annotation was introduced with commit
> 44fa75f207d8a106bc75e6230db61e961fdbf8a8 to be able to operate on power
> indices instead of absolute power values, providing better support for
> different hardware capabilities.
> ```
>
> Not totally sure if that might be relevant to your problem

I checked this patch and it did not solve my issue.

-- 
Best Regards,
Mike Gavrilov.

      reply	other threads:[~2022-09-26 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  0:41 After commit 44fa75f207d8a106bc75e6230db61e961fdbf8a8 Wi-Fi (mt7921e) speed significantly decreased Mikhail Gavrilov
2022-09-26  4:38 ` Thorsten Leemhuis
2022-09-26 10:27   ` Mikhail Gavrilov [this message]

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=CABXGCsPg4mEe0RfJeXCGQ_WatbHgGi16Xw9DFKxPLV8QNi777A@mail.gmail.com \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=jelonek.jonas@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo.bianconi83@gmail.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sean.wang@mediatek.com \
    /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;
as well as URLs for NNTP newsgroup(s).