From: Kalle Valo <kvalo@qca.qualcomm.com>
To: <rmani@qca.qualcomm.com>
Cc: <linux-wireless@vger.kernel.org>,
ath6kl-devel <ath6kl-devel@qualcomm.com>
Subject: Re: [PATCH 1/2] ath6kl: Retain bg scan period value modified by the user
Date: Wed, 18 Apr 2012 13:05:19 +0300 [thread overview]
Message-ID: <4F8E91DF.2000102@qca.qualcomm.com> (raw)
In-Reply-To: <1334572797-6561-1-git-send-email-rmani@qca.qualcomm.com>
On 04/16/2012 01:39 PM, rmani@qca.qualcomm.com wrote:
> From: Raja Mani <rmani@qca.qualcomm.com>
>
> Added a new member bg_scan_period in struct ath6kl_vif
> to retain background scan period value configured via debugfs
> entry 'bgscan_interval'. This backup is needed in schedule scan
> path while configuring scan parameters.
>
> Signed-off-by: Raja Mani <rmani@qca.qualcomm.com>
Thanks, both patches applied. But I did minor improvements to the commit
log in patch 2.
Kalle
prev parent reply other threads:[~2012-04-18 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 10:39 [PATCH 1/2] ath6kl: Retain bg scan period value modified by the user rmani
2012-04-16 10:39 ` [PATCH 2/2] ath6kl: Fix bug in bg scan configuration in schedule scan rmani
2012-04-16 12:31 ` Kalle Valo
2012-04-18 10:05 ` 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=4F8E91DF.2000102@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rmani@qca.qualcomm.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).