From: Kalle Valo <kvalo@codeaurora.org>
To: Amitkumar Karwar <akarwar@marvell.com>
Cc: <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <akarwar@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>
Subject: Re: mwifiex: add missing skb_push() in mwifiex_check_uap_capabilties
Date: Thu, 6 Aug 2015 07:19:50 +0000 (UTC) [thread overview]
Message-ID: <20150806071950.76CC1142033@smtp.codeaurora.org> (raw)
In-Reply-To: <1437998547-3592-1-git-send-email-akarwar@marvell.com>
> For PCIe/USB chipsets, preallocated skb buffers are reused for
> event handling. mwifiex_check_uap_capabilties() performs
> skb_pull(). This patch adds missing skb_push() to restore skb's
> data pointer/length.
>
> This bug was introduced by commit debfc6008169 ("mwifiex: update
> AP WMM settings from BSS_START event")
>
> Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> Signed-off-by: Nishant Sarmukadam <nishants@marvell.com>
Thanks, applied to wireless-drivers-next.git.
Kalle Valo
prev parent reply other threads:[~2015-08-06 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 12:02 [PATCH] mwifiex: add missing skb_push() in mwifiex_check_uap_capabilties Amitkumar Karwar
2015-08-06 7:19 ` 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=20150806071950.76CC1142033@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=akarwar@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 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).