From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Kalle Valo <kvalo@kernel.org>, Wenli Looi <wlooi@ucalgary.ca>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 0/9] ath9k: add support for QCN550x
Date: Wed, 11 May 2022 11:54:39 +0200 [thread overview]
Message-ID: <87lev8wg0w.fsf@toke.dk> (raw)
In-Reply-To: <87lev8y95t.fsf@kernel.org>
Kalle Valo <kvalo@kernel.org> writes:
> Wenli Looi <wlooi@ucalgary.ca> writes:
>
>> Thanks Kalle for the comments.
>>
>> Please let me know if I should resend the patch with the minor changes
>> or if there are additional comments.
>
> The patchset is set to 'Changes Requested' in patchwork:
>
> https://patchwork.kernel.org/project/linux-wireless/list/?series=632942&state=*&order=date
>
> This means you need to submit v2.
Yes, please resubmit with Kalle's comments addressed :)
-Toke
prev parent reply other threads:[~2022-05-11 9:55 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
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 [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=87lev8wg0w.fsf@toke.dk \
--to=toke@toke.dk \
--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 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).