From: Jonas Jelonek <jelonek.jonas@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Thomas Hühn" <thomas.huehn@hs-nordhausen.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
"nbd@nbd.name" <nbd@nbd.name>
Subject: Re: [RFC 0/4] mac80211: add TPC support in control path
Date: Mon, 29 Aug 2022 17:19:45 +0200 [thread overview]
Message-ID: <D322E049-6B08-402D-AB95-982363369028@gmail.com> (raw)
In-Reply-To: <50d80bebabe0ce2413af89af7bf45321ac7f0d6b.camel@sipsolutions.net>
Good point, definitely makes sense.
Would this be sufficient as an implementation for this RFC?
Greetings
Jonas
> On 29. Aug 2022, at 16:52, Johannes Berg <johannes@sipsolutions.net> wrote:
>
> On Mon, 2022-08-29 at 16:52 +0200, Johannes Berg wrote:
>> On Mon, 2022-08-29 at 16:51 +0200, Thomas Hühn wrote:
>>>>>
>>>>> Compile-Tested: current wireless-next tree with all flags on
>>>>> Tested-on PCEngines APU with ath9k WiFi device on OpenWrt Linux
>>>>> Kernel 5.10.137
>>>>>
>>>>
>>>> That seems just a little old? Not sure I'd trust that given the major
>>>> changes in the tree recently?
>>>
>>> Good point, we can test this with 5.15.63 by enabling the OpenWrt testing kernel … would that be ok ?
>>>
>>
>> Well a lot of major changes just happened 5.19 -> 6.0, so something more
>> recent would be better?
>>
>
> Maybe you could add support in hwsim?
>
> johannes
next prev parent reply other threads:[~2022-08-29 15:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 14:41 [RFC 0/4] mac80211: add TPC support in control path Jonas Jelonek
2022-08-29 14:41 ` [RFC 1/4] mac80211: modify tx-power level annotation Jonas Jelonek
2022-08-29 14:41 ` [RFC 2/4] mac80211: add tx-power annotation in control path Jonas Jelonek
2022-08-29 14:41 ` [RFC 3/4] mac80211: add hardware flags for TPC support Jonas Jelonek
2022-08-29 14:41 ` [RFC 4/4] mac80211: add utility function for tx_rate - rate_info conversion Jonas Jelonek
2022-08-29 14:45 ` [RFC 0/4] mac80211: add TPC support in control path Johannes Berg
2022-08-29 14:51 ` Thomas Hühn
2022-08-29 14:52 ` Johannes Berg
2022-08-29 14:52 ` Johannes Berg
2022-08-29 15:19 ` Jonas Jelonek [this message]
2022-08-29 20:31 ` Thomas Hühn
2022-08-29 15:15 ` Jonas Jelonek
2022-08-29 14:46 ` Johannes Berg
2022-08-29 15:06 ` Jonas Jelonek
2022-08-31 13:59 ` Jonas Jelonek
2022-08-31 14:22 ` Johannes Berg
2022-08-31 15:39 ` Jonas Jelonek
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=D322E049-6B08-402D-AB95-982363369028@gmail.com \
--to=jelonek.jonas@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=thomas.huehn@hs-nordhausen.de \
/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