From: Dan Carpenter <dan.carpenter@oracle.com>
To: Marcos Paulo de Souza <marcos.mage@gmail.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@suse.de>,
Forest Bond <forest@alittletooquiet.net>
Subject: Re: [PATCH 1/4] staging: vt6656: channel.c: Remove dead code
Date: Thu, 1 Dec 2011 18:00:03 +0300 [thread overview]
Message-ID: <20111201150003.GI20466@mwanda> (raw)
In-Reply-To: <1322698969-19285-1-git-send-email-marcos.mage@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
On Thu, Dec 01, 2011 at 12:22:49AM +0000, Marcos Paulo de Souza wrote:
> This patch remove some unneeded code. Some comments, for loop doing
> nothing, debug messages and unneeded variables was removed.
>
This rewrites some stuff, it's not just deleting stuff... Yes,
you've rewritten it in a better way, but you should mention that in
the changelog. Maybe break it up into smaller patches or something?
> @@ -463,51 +444,23 @@ void CHvInitChannelTable(void *pDeviceHandler)
>
> if ((pDevice->dwDiagRefCount != 0) ||
> (pDevice->b11hEable == TRUE)) {
> - if (bMultiBand == TRUE) {
> - for (ii = 0; ii < CB_MAX_CHANNEL; ii++) {
> + if (bMultiBand == TRUE)
^
Don't delete the '{' from here. Multi-line indents get {} braces
even though it's not needed for semantic reasons.
I told you that yesterday. :/
> + for (ii = 0; ii < CB_MAX_CHANNEL; ii++)
> sChannelTbl[ii+1].bValid = TRUE;
regards,
dan carpenter
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-12-01 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 0:22 [PATCH 1/4] staging: vt6656: channel.c: Remove dead code Marcos Paulo de Souza
2011-12-01 15:00 ` Dan Carpenter [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=20111201150003.GI20466@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcos.mage@gmail.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