All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: linux-wireless@vger.kernel.org,
	Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
	Avinash Patil <avinashp@quantenna.com>
Subject: Re: [v2,01/10] qtnfmac: check that MAC exists in regulatory notifier
Date: Tue,  9 Jan 2018 12:12:47 +0000 (UTC)	[thread overview]
Message-ID: <20180109121247.C95116081B@smtp.codeaurora.org> (raw)
In-Reply-To: <20171219112856.22463-2-sergey.matyukevich.os@quantenna.com>

Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> wrote:

> From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
> 
> It is possible that regulatory notifier is called before MAC data
> was allocated. We need to verify that MAC data exists before trying
> to send a regulatory change event.
> 
> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>

10 patches applied to wireless-drivers-next.git, thanks.

4fd045cdb239 qtnfmac: check that MAC exists in regulatory notifier
5bf374ab91ad qtnfmac: pass complete channel data between driver and firmware
b05ee456fd21 qtnfmac: add support for radar detection and CAC
e6ef8cd05145 qtnfmac: change default interface mode from AP to STA
e6e594aff26a qtnfmac: check for passed channel being NULL in MGMT_TX command
fbad963a28e4 qtnfmac: fix rssi data passed to wireless core
9cbd599966d8 qtnfmac: fill wiphy's extended capabilities
4d2a7a1cfa68 qtnfmac: modify GET_STA_STATS cmd format for back/forward compatibility
7a4d3a3bc84e qtnfmac: keeping track of "generation" for STA info
f1398fd2dd8c qtnfmac: support MAC address based access control

-- 
https://patchwork.kernel.org/patch/10123079/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2018-01-09 12:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 11:28 [PATCH v2 0/10] qtnfmac: regular portion of fixes and features Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 01/10] qtnfmac: check that MAC exists in regulatory notifier Sergey Matyukevich
2018-01-09 12:12   ` Kalle Valo [this message]
2018-01-09 13:09     ` [v2,01/10] " Sergey Matyukevich
2018-01-09 15:05       ` Kalle Valo
2017-12-19 11:28 ` [PATCH v2 02/10] qtnfmac: pass complete channel data between driver and firmware Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 03/10] qtnfmac: add support for radar detection and CAC Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 04/10] qtnfmac: change default interface mode from AP to STA Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 05/10] qtnfmac: check for passed channel being NULL in MGMT_TX command Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 06/10] qtnfmac: fix rssi data passed to wireless core Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 07/10] qtnfmac: fill wiphy's extended capabilities Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 08/10] qtnfmac: modify GET_STA_STATS cmd format for back/forward compatibility Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 09/10] qtnfmac: keeping track of "generation" for STA info Sergey Matyukevich
2017-12-19 11:28 ` [PATCH v2 10/10] qtnfmac: support MAC address based access control Sergey Matyukevich

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=20180109121247.C95116081B@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=avinashp@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sergey.matyukevich.os@quantenna.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 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.