From: Joe Perches <joe@perches.com>
To: "Pedersen, Thomas" <c_tpeder@qca.qualcomm.com>
Cc: kvalo@qca.qualcomm.com, linux-wireless@vger.kernel.org,
ath6kl-devel@qualcomm.com
Subject: Re: [PATCH v2] ath6kl: enable enhanced bmiss detection
Date: Mon, 14 May 2012 11:08:26 -0700 [thread overview]
Message-ID: <1337018906.29436.27.camel@joe2Laptop> (raw)
In-Reply-To: <20120514180339.GA4030@pista>
On Mon, 2012-05-14 at 11:03 -0700, Pedersen, Thomas wrote:
> On Mon, May 14, 2012 at 10:56:59AM -0700, Joe Perches wrote:
> > On Mon, 2012-05-14 at 10:47 -0700, Thomas Pedersen wrote:
> > > Enable enhanced bmiss detection if the firmware supports it. This
> > > feature is only enabled on some firmwares since it comes with a power
> > > cost.
> > []
> > > diff --git a/drivers/net/wireless/ath/ath6kl/cfg80211.c b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> > []
> > > @@ -2614,6 +2619,30 @@ static int ath6kl_set_channel(struct wiphy *wiphy, struct net_device *dev,
> > > return 0;
> > > }
> > >
> > > +void ath6kl_cfg80211_sta_bmiss_enhance(struct ath6kl_vif *vif, bool enable)
[]
> > Why 2 messages when 1 message might do?
> >
> > err = ath6kl_wmi_sta_bmiss_enhance_cmd(vif->ar->wmi,
> > vif->fw_vif_idx, enable);
> > ath6kl_dbg(ATH6KL_DBG_WLAN_CFG,
> > "%s enhanced fw bmiss detection: %s\n",
> > enable ? "enable" : "disable",
> > err ? "OK" : "failed");
>
> OK that seems nicer. Should we still print the error code, or maybe it
> doesn't really matter?
Hi Thomas.
That's up to you. I don't know the code at all.
btw: the err ?: output is badly reversed in my example.
next prev parent reply other threads:[~2012-05-14 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 17:47 [PATCH v2] ath6kl: enable enhanced bmiss detection Thomas Pedersen
2012-05-14 17:56 ` Joe Perches
2012-05-14 18:03 ` Pedersen, Thomas
2012-05-14 18:08 ` Joe Perches [this message]
2012-05-14 18:09 ` Kalle Valo
2012-05-14 18:31 ` Pedersen, Thomas
2012-05-15 4:28 ` Kalle Valo
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=1337018906.29436.27.camel@joe2Laptop \
--to=joe@perches.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=c_tpeder@qca.qualcomm.com \
--cc=kvalo@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).