From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: <linux-wireless@vger.kernel.org>,
Nishant Sarmukadam <nishants@marvell.com>,
Ganapathi Bhat <gbhat@marvell.com>,
Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: mwifiex: Avoid skipping WEP key deletion for AP
Date: Tue, 7 Feb 2017 08:03:58 +0000 (UTC) [thread overview]
Message-ID: <20170207080358.C6EE7609F2@smtp.codeaurora.org> (raw)
In-Reply-To: <1486126822-21958-1-git-send-email-akarwar@marvell.com>
Amitkumar Karwar <akarwar@marvell.com> wrote:
> From: Ganapathi Bhat <gbhat@marvell.com>
>
> This patch fixes the issue specific to AP. AP is started with WEP
> security and external station is connected to it. Data path works
> in this case. Now if AP is restarted with WPA/WPA2 security,
> station is able to connect but ping fails.
>
> Driver skips the deletion of WEP keys if interface type is AP.
> Removing that redundant check resolves the issue.
>
> Fixes: e57f1734d87a ("mwifiex: add key material v2 support")
> Signed-off-by: Ganapathi Bhat <gbhat@marvell.com>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
Patch applied to wireless-drivers-next.git, thanks.
a5b60de6972d mwifiex: Avoid skipping WEP key deletion for AP
--
https://patchwork.kernel.org/patch/9554057/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2017-02-07 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 13:00 [PATCH] mwifiex: Avoid skipping WEP key deletion for AP Amitkumar Karwar
2017-02-07 8:03 ` Kalle Valo [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=20170207080358.C6EE7609F2@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@marvell.com \
--cc=gbhat@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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.