linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Maya Haim <merez@qti.qualcomm.com>
Cc: qca_merez <qca_merez@qca.qualcomm.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	wil6210 <wil6210@qca.qualcomm.com>,
	qca_liord <qca_liord@qca.qualcomm.com>
Subject: Re: [PATCH v2 4/5] wil6210: add option to ignore OTA regulatory hints
Date: Mon, 22 May 2017 14:22:57 +0000	[thread overview]
Message-ID: <871srhug1z.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <71d0595982f24c12b519fa67ea6f0ad8@euamsexm01a.eu.qualcomm.com> (Maya Haim's message of "Sun, 21 May 2017 20:07:32 +0000")

Maya Haim <merez@qti.qualcomm.com> writes:

> kvalo@qca.qualcomm.com wrote:
>>=20
>> I wonder should something like this be in cfg80211? Because I doubt
>> wil6210 is the only driver having this problem.
>
> We will check that and share our conclusions.
> Can you please drop this patch for now and apply the rest of the patches
> (if there are no additional comments)?

Sure, I have now dropped this patch. The rest are still on my queue.

--=20
Kalle Valo=

  reply	other threads:[~2017-05-22 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 11:45 [PATCH v2 0/5] wil6210 patches Maya Erez
2017-05-15 11:45 ` [PATCH v2 1/5] wil6210: low level RF sector API Maya Erez
2017-05-23 15:31   ` [v2,1/5] " Kalle Valo
2017-05-15 11:45 ` [PATCH v2 2/5] wil6210: add option to load FTM FW Maya Erez
2017-05-15 11:45 ` [PATCH v2 3/5] wil6210: Improve AP stop handling Maya Erez
2017-05-15 11:45 ` [PATCH v2 4/5] wil6210: add option to ignore OTA regulatory hints Maya Erez
2017-05-19  4:56   ` Kalle Valo
2017-05-21 20:07     ` Maya Haim
2017-05-22 14:22       ` Kalle Valo [this message]
2017-05-15 11:45 ` [PATCH v2 5/5] wil6210: support devices with different PCIe bar size Maya Erez

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=871srhug1z.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=merez@qti.qualcomm.com \
    --cc=qca_liord@qca.qualcomm.com \
    --cc=qca_merez@qca.qualcomm.com \
    --cc=wil6210@qca.qualcomm.com \
    /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).