From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: vh.nguyen@actiasodielec.fr, linux-wireless@vger.kernel.org,
svens@stackframe.org, ath10k@lists.infradead.org
Subject: Re: [RFC/RFT 1/2] ath10k: fix monitor start/stop sequences
Date: Mon, 21 Jul 2014 20:39:26 +0300 [thread overview]
Message-ID: <87d2cyy5kh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1405516873-26411-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Wed, 16 Jul 2014 15:21:12 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Fix some cases where monitor start failure left
> the driver in a confused state.
>
> This also makes the monitor code simpler.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
From a quick review looks good to me. Are you planning to submit this as
a proper patch at some point?
Did anyone test this?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <vh.nguyen@actiasodielec.fr>,
<svens@stackframe.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [RFC/RFT 1/2] ath10k: fix monitor start/stop sequences
Date: Mon, 21 Jul 2014 20:39:26 +0300 [thread overview]
Message-ID: <87d2cyy5kh.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1405516873-26411-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Wed, 16 Jul 2014 15:21:12 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Fix some cases where monitor start failure left
> the driver in a confused state.
>
> This also makes the monitor code simpler.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
>From a quick review looks good to me. Are you planning to submit this as
a proper patch at some point?
Did anyone test this?
--
Kalle Valo
next prev parent reply other threads:[~2014-07-21 17:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 13:21 [RFC/RFT 1/2] ath10k: fix monitor start/stop sequences Michal Kazior
2014-07-16 13:21 ` Michal Kazior
2014-07-16 13:21 ` [RFC/RFT 2/2] ath10k: don't start monitor vdev for promisc Michal Kazior
2014-07-16 13:21 ` Michal Kazior
2014-07-16 15:28 ` Ben Greear
2014-07-16 15:28 ` Ben Greear
2014-07-17 5:15 ` Michal Kazior
2014-07-17 5:15 ` Michal Kazior
2014-07-21 17:39 ` Kalle Valo [this message]
2014-07-21 17:39 ` [RFC/RFT 1/2] ath10k: fix monitor start/stop sequences Kalle Valo
2014-07-22 8:14 ` Michal Kazior
2014-07-22 8:14 ` Michal Kazior
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=87d2cyy5kh.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=svens@stackframe.org \
--cc=vh.nguyen@actiasodielec.fr \
/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.