From: Kalle Valo <kvalo@codeaurora.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org,
bryan.odonoghue@linaro.org, shawn.guo@linaro.org,
loic.poulain@linaro.org
Subject: Re: [PATCH v5 1/2] wcn36xx: Add VHT fields to parameter data structures
Date: Mon, 21 Sep 2020 13:13:41 +0000 (UTC) [thread overview]
Message-ID: <20200921131341.4E1F3C433FF@smtp.codeaurora.org> (raw)
In-Reply-To: <20200910150450.2178784-2-bryan.odonoghue@linaro.org>
Bryan O'Donoghue <bryan.odonoghue@linaro.org> wrote:
> In order to pass VHT parameters to wcn3680 we need to use a super-set of
> the V1 data-structures with additional VHT parameters tacked on.
>
> This patch adds the additional fields to the STA and BSS parameter
> structures.
>
> Since neither wcn3620 nor wcn3660 support VHT the size of the passed
> message is fixed to the previous message length. Subsequent changes will
> differentiate between wcn3620/wcn3660 and wcn3680 which does use the larger
> message size.
>
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
2 patches applied to ath-next branch of ath.git, thanks.
96d6617d64ee wcn36xx: Add VHT fields to parameter data structures
617e7cf80c92 wcn36xx: Use V1 data structure to store supported rates
--
https://patchwork.kernel.org/patch/11768987/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-09-21 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 15:04 [PATCH v5 0/2] wcn36xx: Extend V1 data-structures Bryan O'Donoghue
2020-09-10 15:04 ` [PATCH v5 1/2] wcn36xx: Add VHT fields to parameter data structures Bryan O'Donoghue
2020-09-21 13:13 ` Kalle Valo [this message]
2020-09-10 15:04 ` [PATCH v5 2/2] wcn36xx: Use V1 data structure to store supported rates Bryan O'Donoghue
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=20200921131341.4E1F3C433FF@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=bryan.odonoghue@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=shawn.guo@linaro.org \
--cc=wcn36xx@lists.infradead.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 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.