All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sriram R <srirrama@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: [PATCH] ath11k: Remove probe response offload template setup
Date: Thu, 06 Jun 2019 19:47:07 +0300	[thread overview]
Message-ID: <87d0jqveyc.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20190606164126.5EA7D60CED@smtp.codeaurora.org> (Kalle Valo's message of "Thu, 6 Jun 2019 16:41:26 +0000 (UTC)")

Kalle Valo <kvalo@codeaurora.org> writes:

> Sriram R <srirrama@codeaurora.org> wrote:
>
>> Probe response offload support is not supported by
>> IPQ8074 firmware. Hence do not advertise or set probe
>> response template to the firmware.
>> 
>> This would avoid the below error during template setup.
>> 'failed to update prb tmpl -1'
>> 
>> Signed-off-by: Sriram R <srirrama@codeaurora.org>
>
> New warnings:
>
> drivers/net/wireless/ath/ath11k/wmi.c:4597:34: warning: mixing different enum types
> drivers/net/wireless/ath/ath11k/wmi.c:4597:34:     unsigned int enum dfs_reg versus
> drivers/net/wireless/ath/ath11k/wmi.c:4597:34:     unsigned int enum ath11k_dfs_region
>
> Patch set to Changes Requested.

Actually I'll take that back, I don't drop this patch. I got confused
which commit caused those. It's actually this one:

b0d742f32bc3 ath11k: Fix vdev start failure when operating in CN, KR regdomain

-- 
Kalle Valo

_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2019-06-06 16:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 11:38 [PATCH] ath11k: Remove probe response offload template setup Sriram R
2019-06-06 16:41 ` Kalle Valo
2019-06-06 16:47   ` Kalle Valo [this message]
2019-06-06 16:49 ` Kalle Valo

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=87d0jqveyc.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=srirrama@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 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.