From: Luciano Coelho <coelho@ti.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3.1] wl12xx: add max_sched_scan_ssids value to the hw description
Date: Tue, 23 Aug 2011 11:44:50 +0300 [thread overview]
Message-ID: <1314089090.2296.127.camel@cumari> (raw)
In-Reply-To: <1314088945-19848-1-git-send-email-coelho@ti.com>
Hi John,
On Tue, 2011-08-23 at 11:42 +0300, Luciano Coelho wrote:
> After commit 5a865ba, we require a separate value to indicate the
> number of supported SSIDs in scheduled scans. This patch adds a
> proper value to the wl12xx driver.
>
> This fixes a regression in 3.1-rc3 where scheduled scans were not
> working properly with the wl12xx driver.
>
> Signed-off-by: Luciano Coelho <coelho@ti.com>
> ---
Could you please apply this patch to 3.1 too? For some reason I didn't
push my change in the wl12xx driver after I made the changes to include
max_sched_scan_ssids in the hw configuration.
This is a one-liner very trivial patch that fixes a regression, so I
hope it's still okay to get it in.
--
Cheers,
Luca.
prev parent reply other threads:[~2011-08-23 8:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 8:42 [PATCH 3.1] wl12xx: add max_sched_scan_ssids value to the hw description Luciano Coelho
2011-08-23 8:44 ` Luciano Coelho [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=1314089090.2296.127.camel@cumari \
--to=coelho@ti.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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