All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rtlwifi: rtl8188ee: Add new driver
Date: Mon, 08 Apr 2013 17:24:46 -0500	[thread overview]
Message-ID: <516343AE.6020503@lwfinger.net> (raw)
In-Reply-To: <20130407093859.GA28809@longonot.mountain>

On 04/07/2013 04:39 AM, Dan Carpenter wrote:
> Hi Larry,
>
> I had a question about f0eb856e0b6c: "rtlwifi: rtl8188ee: Add new
> driver" from Mar 24, 2013.
>
> drivers/net/wireless/rtlwifi/rtl8188ee/hw.c
>    1631          for (path = 0; path < MAX_RF_PATH; path++) {
>    1632                  /*2.4G default value*/
>    1633                  for (i = 0; i < MAX_CHNL_GROUP_24G; i++) {
>    1634                          pwr2g->index_cck_base[path][i] = hwinfo[eadr++];
>    1635                          if (pwr2g->index_cck_base[path][i] == 0xFF)
>    1636                                  pwr2g->index_cck_base[path][i] = 0x2D;
>    1637                  }
>    1638                  for (i = 0; i < MAX_CHNL_GROUP_24G-1; i++) {
>                                          ^^^^^^^^^^^^^^^^^^^^
> We skip the last element of the array.  It's declared on the stack in
> the caller function so it just has uninitialized stack data.  It doesn't
> look intentional to me.
>
>    1639                          pwr2g->index_bw40_base[path][i] = hwinfo[eadr++];
>    1640                          if (pwr2g->index_bw40_base[path][i] == 0xFF)
>    1641                                  pwr2g->index_bw40_base[path][i] = 0x2D;
>    1642                  }
>
> regards,

Dan,

Thanks for noticing this difference. I agree that there is no reason for any 
difference in the range os the two loops.

I will submit a patch.

Larry



      reply	other threads:[~2013-04-08 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07  9:39 rtlwifi: rtl8188ee: Add new driver Dan Carpenter
2013-04-08 22:24 ` 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=516343AE.6020503@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=dan.carpenter@oracle.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.