From: Johannes Berg <johannes@sipsolutions.net>
To: Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>
Cc: linux-wireless@vger.kernel.org, daniel.lezcano@linaro.org,
daniel.thompson@linaro.org
Subject: Re: [PATCH] cfg80211: wext does not need to set monitor channel in managed mode
Date: Wed, 11 Jan 2017 14:15:14 +0100 [thread overview]
Message-ID: <1484140514.29931.4.camel@sipsolutions.net> (raw)
In-Reply-To: <1483971949-10014-1-git-send-email-jorge.ramirez-ortiz@linaro.org> (sfid-20170109_152601_854161_50F0F778)
On Mon, 2017-01-09 at 15:25 +0100, Jorge Ramirez-Ortiz wrote:
> There is not a valid reason to attempt setting the monitor channel
> while in managed mode. Since this code path only deals with this
> mode,
> remove the code block.
>
Applied.
johannes
prev parent reply other threads:[~2017-01-11 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 14:25 [PATCH] cfg80211: wext does not need to set monitor channel in managed mode Jorge Ramirez-Ortiz
2017-01-11 13:15 ` Johannes Berg [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=1484140514.29931.4.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=daniel.lezcano@linaro.org \
--cc=daniel.thompson@linaro.org \
--cc=jorge.ramirez-ortiz@linaro.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