From: "Pedersen, Thomas" <c_tpeder@qca.qualcomm.com>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: Joe Perches <joe@perches.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:31:24 -0700 [thread overview]
Message-ID: <20120514183124.GA4057@pista> (raw)
In-Reply-To: <4FB14A4D.1030002@qca.qualcomm.com>
On Mon, May 14, 2012 at 09:09:17PM +0300, Kalle Valo wrote:
> On 05/14/2012 09:03 PM, Pedersen, Thomas wrote:
> > On Mon, May 14, 2012 at 10:56:59AM -0700, Joe Perches wrote:
> >
> >> 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?
>
> I missed this in the original review, but it's actually better to not
> use ath6kl_dbg() for error messages. They are more difficult to notice
> that way.
>
> Or did you have a specific reason for using ath6kl_dbg()?
No, you're right. However, if we consolidate these messages they will
both be under ath6kl_dbg() or ath6kl_err(), and neither one would be
correct.
How about just keeping these separate and printing the error through
ath6kl_err()?
Thomas
next prev parent reply other threads:[~2012-05-14 18:31 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
2012-05-14 18:09 ` Kalle Valo
2012-05-14 18:31 ` Pedersen, Thomas [this message]
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=20120514183124.GA4057@pista \
--to=c_tpeder@qca.qualcomm.com \
--cc=ath6kl-devel@qualcomm.com \
--cc=joe@perches.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.