From: Larry Finger <Larry.Finger@lwfinger.net>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Some funny code in brcmsmac
Date: Wed, 14 Dec 2011 15:22:47 -0600 [thread overview]
Message-ID: <4EE913A7.60708@lwfinger.net> (raw)
In-Reply-To: <4EE9036A.7000309@broadcom.com>
On 12/14/2011 02:13 PM, Arend van Spriel wrote:
> Yep. That looks pretty useless to me ;-) I will send a code-redux patch
> for this. Feel free to share these kind of observations in a patch email
> (so I can remain my lazy self and ack it ;-) ).
OK. Actually, a patch would have been easier than a big edit on a
copy-and-paste. My only problem was whether the code that was specific to the
conditions was better, of if it is correct to always use the maximum power.
Larry
prev parent reply other threads:[~2011-12-14 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 4:19 Some funny code in brcmsmac Larry Finger
2011-12-14 20:13 ` Arend van Spriel
2011-12-14 21:22 ` Larry Finger [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=4EE913A7.60708@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=frankyl@broadcom.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.