From: Kalle Valo <kvalo@kernel.org>
To: Wenli Looi <wlooi@ucalgary.ca>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
linux-wireless@vger.kernel.org, ath9k-devel@qca.qualcomm.com
Subject: Re: [PATCH 2/9] ath9k: basic support for QCN550x
Date: Wed, 20 Apr 2022 15:01:04 +0300 [thread overview]
Message-ID: <87pmlcnev3.fsf@kernel.org> (raw)
In-Reply-To: <20220418071313.882179-3-wlooi@ucalgary.ca> (Wenli Looi's message of "Mon, 18 Apr 2022 00:13:06 -0700")
Wenli Looi <wlooi@ucalgary.ca> writes:
> QCN550x is very similar to QCA956x. Note that AR_CH0_XTAL is
> intentionally unchanged. Certain arrays are no longer static because
> they are no longer constant.
s-o-b missing in patches 2-5.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-04-20 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 7:13 [PATCH 0/9] ath9k: add support for QCN550x Wenli Looi
2022-04-18 7:13 ` [PATCH 1/9] ath9k: add QCN550x device IDs Wenli Looi
2022-04-20 12:00 ` Kalle Valo
2022-04-18 7:13 ` [PATCH 2/9] ath9k: basic support for QCN550x Wenli Looi
2022-04-20 12:01 ` Kalle Valo [this message]
2022-04-18 7:13 ` [PATCH 3/9] ath9k: add QCN550x initvals Wenli Looi
2022-04-18 7:13 ` [PATCH 4/9] ath9k: implement QCN550x rx Wenli Looi
2022-04-18 7:13 ` [PATCH 5/9] ath9k: implement QCN550x tx Wenli Looi
2022-04-18 7:13 ` [PATCH 6/9] ath9k: group some ar9300 eeprom functions at the top Wenli Looi
2022-04-18 7:13 ` [PATCH 7/9] ath9k: add abstractions over ar9300 eeprom Wenli Looi
2022-04-18 7:13 ` [PATCH 8/9] ath9k: rename ar9300_eeprom to ar9300_eeprom_v1 Wenli Looi
2022-04-18 7:13 ` [PATCH 9/9] ath9k: add ar9300_eeprom_v2 Wenli Looi
2022-05-10 18:39 ` [PATCH 0/9] ath9k: add support for QCN550x Wenli Looi
2022-05-11 4:39 ` Kalle Valo
2022-05-11 9:54 ` Toke Høiland-Jørgensen
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=87pmlcnev3.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath9k-devel@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=toke@toke.dk \
--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.