From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Thomas Pedersen <c_tpeder@qca.qualcomm.com>
Cc: <ath6kl-devel@qualcomm.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath6kl: fix fw capability parsing
Date: Thu, 14 Jun 2012 13:56:46 +0300 [thread overview]
Message-ID: <4FD9C36E.50302@qca.qualcomm.com> (raw)
In-Reply-To: <1339446972-3793-1-git-send-email-c_tpeder@qca.qualcomm.com>
On 06/11/2012 11:36 PM, Thomas Pedersen wrote:
> This patch fixes a bug where no capabilites are parsed when the number
> of firmware capability bits translate into fewer bytes than the host has
> knowledge of. Instead just process number of capability bytes as
> reported by the firmware.
>
> Signed-off-by: Thomas Pedersen <c_tpeder@qca.qualcomm.com>
Thanks, applied.
Kalle
prev parent reply other threads:[~2012-06-14 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 20:36 [PATCH] ath6kl: fix fw capability parsing Thomas Pedersen
2012-06-14 10:56 ` 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=4FD9C36E.50302@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=c_tpeder@qca.qualcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).