From: Joe Perches <joe@perches.com>
To: Dave Perez <dave@daveperez.com>
Cc: gregkh@linuxfoundation.org, tapaswenipathak@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4573/4573] Staging: rtl8188eu: fixed newlines after declarations
Date: Wed, 29 Jul 2015 22:38:36 -0700 [thread overview]
Message-ID: <1438234716.2677.8.camel@perches.com> (raw)
In-Reply-To: <1438220082-4599-1-git-send-email-dave@daveperez.com>
On Wed, 2015-07-29 at 21:34 -0400, Dave Perez wrote:
> This is a patch to the rtw_debug.c file that fixes styling errors relating to new lines after variable declarations.
[]
> diff --git a/drivers/staging/rtl8188eu/core/rtw_debug.c b/drivers/staging/rtl8188eu/core/rtw_debug.c
[]
> @@ -219,6 +219,7 @@ int proc_get_ht_option(char *page, char **start,
> struct mlme_priv *pmlmepriv = &(padapter->mlmepriv);
>
> int len = 0;
> +
> len += snprintf(page + len, count - len, "ht_option=%d\n", pmlmepriv->htpriv.ht_option);
> *eof = 1;
> return len;
the blank line before "int len = 0" could also be removed.
The routine _could_ be rewritten more simply as:
struct mlme_priv *pmlmepriv = &padapter->mlmepriv;
int len = snprintf(page, count, "ht_option=%d\n",
pmlmepriv->htpriv.htoption);
*eof = 1;
return len;
}
but there are a bunch of other routines that use this form
so it's probably fine as-is.
prev parent reply other threads:[~2015-07-30 5:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 1:34 [PATCH 4573/4573] Staging: rtl8188eu: fixed newlines after declarations Dave Perez
2015-07-30 1:41 ` Greg KH
2015-07-30 5:38 ` Joe Perches [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=1438234716.2677.8.camel@perches.com \
--to=joe@perches.com \
--cc=dave@daveperez.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tapaswenipathak@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 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.