From: Aloka Dixit <alokad@codeaurora.org>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, John Crispin <john@phrozen.org>,
Lavanya Suresh <lavaks@codeaurora.org>,
ath11k@lists.infradead.org, kvalo=codeaurora.org@codeaurora.org
Subject: Re: [PATCH V6] ath11k: add multiple bssid support
Date: Mon, 01 Feb 2021 10:22:08 -0800 [thread overview]
Message-ID: <7b36901091429419209653f1be21cce1@codeaurora.org> (raw)
In-Reply-To: <874kj3bo65.fsf@codeaurora.org>
On 2021-01-26 09:31, Kalle Valo wrote:
> Aloka Dixit <alokad@codeaurora.org> writes:
>
>> From: John Crispin <john@phrozen.org>
>>
>> Add the required wmi support and make use of it in the beacon template
>> code. We need to split the beacon code up into 2 code paths so that
>> we can also send EMA templates.
>>
>> Tested-on: IPQ8074 hw2.0 AHB
>> WLAN.HK.2.4.0.1-01492-QCAHKSWPL_SILICONZ-1
>>
>> Signed-off-by: John Crispin <john@phrozen.org>
>> Signed-off-by: Lavanya Suresh <lavaks@codeaurora.org>
>> Signed-off-by: Aloka Dixit <alokad@codeaurora.org>
>
> Please CC ath11k list with ath11k patches.
>
>> base-commit: be8cd9b8f5ed435c27530430aa1b1da30f9825d5
>> prerequisite-patch-id: 1c9127eb0d6efce75a0aa085527bf81ced427387
>> prerequisite-patch-id: 41af1c46bdedfa8768dd4205bb0647101de27dea
>> prerequisite-patch-id: f197607d75899cbecffd775e1ca243aa2fe082d0
>> prerequisite-patch-id: 55dad75c4f560213110f57f1abf24d9b7301a1b2
>
> This fails to compile for me, what are these prerequisite patches?
The prerequisites are these:
https://patchwork.kernel.org/project/linux-wireless/list/?series=417275
Compilation shouldn't have failed though. Once these are accepted, will
send rebased version for ath11k.
Thanks.
prev parent reply other threads:[~2021-02-01 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 0:32 [PATCH V6] ath11k: add multiple bssid support Aloka Dixit
2021-01-26 17:31 ` Kalle Valo
2021-02-01 18:22 ` Aloka Dixit [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=7b36901091429419209653f1be21cce1@codeaurora.org \
--to=alokad@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=john@phrozen.org \
--cc=kvalo=codeaurora.org@codeaurora.org \
--cc=kvalo@codeaurora.org \
--cc=lavaks@codeaurora.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).