From: Kalle Valo <kvalo@codeaurora.org>
To: John Crispin <john@phrozen.org>
Cc: Miles Hu <milehu@codeaurora.org>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [PATCH V2 3/3] ath11k: add support for setting fixed HE rate/gi/ltf
Date: Tue, 11 Feb 2020 15:15:43 +0200 [thread overview]
Message-ID: <87d0alxo1s.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20200204103514.18111-3-john@phrozen.org> (John Crispin's message of "Tue, 4 Feb 2020 11:35:14 +0100")
John Crispin <john@phrozen.org> writes:
> From: Miles Hu <milehu@codeaurora.org>
>
> This patch adds ath11k support for setting fixed HE rate/gi/ltf values that
> we are now able to send to the kernel using nl80211. The added code is
> reusing parts of the existing code path already used for HT/VHT. The new
> helpers are symmetric to how we do it for HT/VHT.
>
> Signed-off-by: John Crispin <john@phrozen.org>
> Signed-off-by: Miles Hu <milehu@codeaurora.org>
s-o-b lines in incorrect order, Miles' tag (being the author) should be
first.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-02-11 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 10:35 [PATCH V2 1/3] nl80211: add support for setting fixed HE rate/gi/ltf John Crispin
2020-02-04 10:35 ` [PATCH V2 2/3] mac80211: " John Crispin
2020-02-14 9:04 ` Johannes Berg
2020-02-04 10:35 ` [PATCH V2 3/3] ath11k: " John Crispin
2020-02-11 13:15 ` Kalle Valo [this message]
2020-02-06 8:58 ` [PATCH V2 1/3] nl80211: " Arend Van Spriel
2020-02-06 9:04 ` John Crispin
2020-02-06 9:06 ` Arend Van Spriel
2020-02-14 9:03 ` Johannes Berg
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=87d0alxo1s.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=john@phrozen.org \
--cc=linux-wireless@vger.kernel.org \
--cc=milehu@codeaurora.org \
/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