From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Wenli Looi <wlooi@ucalgary.ca>
Cc: Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com,
Wenli Looi <wlooi@ucalgary.ca>
Subject: Re: [PATCH 6/6] ath9k: add functions to get paprd rate mask
Date: Mon, 21 Mar 2022 17:03:24 +0100 [thread overview]
Message-ID: <87sfrb8f8z.fsf@toke.dk> (raw)
In-Reply-To: <20220320233010.123106-7-wlooi@ucalgary.ca>
Wenli Looi <wlooi@ucalgary.ca> writes:
> This removes some code duplication with le32_to_cpu. This may also be
> required for QCN550x support, to provide an abstraction over the
> underlying EEPROM format.
>
> Signed-off-by: Wenli Looi <wlooi@ucalgary.ca>
Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
prev parent reply other threads:[~2022-03-21 16:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 23:30 [PATCH 0/6] ath9k: suggested improvements and bugfixes Wenli Looi
2022-03-20 23:30 ` [PATCH 1/6] ath9k: make ATH_SREV macros more consistent Wenli Looi
2022-03-21 16:02 ` Toke Høiland-Jørgensen
2022-03-25 10:34 ` Kalle Valo
2022-03-20 23:30 ` [PATCH 2/6] ath9k: split set11nRateFlags and set11nChainSel Wenli Looi
2022-03-21 16:02 ` Toke Høiland-Jørgensen
2022-03-20 23:30 ` [PATCH 3/6] ath9k: use AR9300_MAX_CHAINS when appropriate Wenli Looi
2022-03-21 16:02 ` Toke Høiland-Jørgensen
2022-03-20 23:30 ` [PATCH 4/6] ath9k: fix ar9003_get_eepmisc Wenli Looi
2022-03-21 15:51 ` Toke Høiland-Jørgensen
2022-03-21 19:57 ` Wenli Looi
2022-03-21 21:07 ` Toke Høiland-Jørgensen
2022-03-21 21:07 ` Toke Høiland-Jørgensen
2022-03-23 9:30 ` Kalle Valo
2022-03-23 11:15 ` Toke Høiland-Jørgensen
2022-03-23 12:16 ` Kalle Valo
2022-03-23 12:34 ` Toke Høiland-Jørgensen
2022-03-24 15:51 ` Wenli Looi
2022-03-20 23:30 ` [PATCH 5/6] ath9k: refactor ar9003_hw_spur_mitigate_ofdm Wenli Looi
2022-03-21 16:03 ` Toke Høiland-Jørgensen
2022-03-20 23:30 ` [PATCH 6/6] ath9k: add functions to get paprd rate mask Wenli Looi
2022-03-21 16:03 ` Toke Høiland-Jørgensen [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=87sfrb8f8z.fsf@toke.dk \
--to=toke@toke.dk \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wlooi@ucalgary.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.