From: Joe Perches <joe@perches.com>
To: sanjeev sharma <sanjeevsharmaengg@gmail.com>
Cc: gregkh@linuxfoundation.org, rmfrfs@gmail.com,
peter.senna@gmail.com, teobaluta@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
sanjeev sharma <sanjeev_sharma@mentor.com>
Subject: Re: [PATCH v3 4/4] staging: rtl8192u: Fixed too long lines
Date: Wed, 09 Jul 2014 05:56:52 -0700 [thread overview]
Message-ID: <1404910612.932.95.camel@joe-AO725> (raw)
In-Reply-To: <1404908382-7043-5-git-send-email-sanjeevsharmaengg@gmail.com>
On Wed, 2014-07-09 at 17:49 +0530, sanjeev sharma wrote:
> This patch will fix too long lines warning
> reported by checkpatch.pl.
Hi Sanjeev.
> diff --git a/drivers/staging/rtl8192u/r819xU_phy.c b/drivers/staging/rtl8192u/r819xU_phy.c
[]
> @@ -1786,7 +1788,9 @@ void InitialGainOperateWorkItemCallBack(struct work_struct *work)
> RT_TRACE(COMP_SCAN, "Scan BBInitialGainRestore 0xa0a is %x\n",
> priv->initgain_backup.cca);
>
> - rtl8192_phy_setTxPower(dev, priv->ieee80211->current_network.channel);
> + rtl8192_phy_setTxPower(dev,
> + priv->ieee80211->current_network.channel
> + );
This one is a little off
+ rtl8192_phy_setTxPower(dev,
+ priv->ieee80211->current_network.channel
+ );
Please align multiline statements to the appropriate
open parenthesis using a mix of initial leading tabs
followed by the minimal number of spaces required
to put the first non-whitespace char at the column
immediately after the preceding open paren.
Here it's 4 tabs, 7 spaces, not 5 tabs:
+ rtl8192_phy_setTxPower(dev,
+ priv->ieee80211->current_network.channel);
And please don't use a line that's just a close
parenthesis and semicolon.
I think it's better to ignore the 80 column limit for
these and place them at the end of the preceding line.
next prev parent reply other threads:[~2014-07-09 12:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 6:04 [PATCH] staging: rtl8192u: fix checkpatch error/warning in r819xU_phy.c sanjeev sharma
2014-07-08 7:43 ` Dan Carpenter
[not found] ` <CAGUYZuQgpNQRRg5X_AYv_iW5W60EdEwo0VOe3EJAPJocKrTf3g@mail.gmail.com>
2014-07-08 10:01 ` Dan Carpenter
2014-07-09 6:04 ` [PATCH v2 0/4] Fix checkpatch reported problem " sanjeev sharma
2014-07-09 6:04 ` [PATCH v2 1/4] staging: rtl8192u: Remove useless return statement " sanjeev sharma
2014-07-09 8:09 ` Dan Carpenter
2014-07-09 10:14 ` Sharma, Sanjeev
2014-07-09 6:04 ` [PATCH v2 2/4] staging: rtl8192u: Removed unnecessary whitespace & tab warning " sanjeev sharma
2014-07-09 6:04 ` [PATCH v2 3/4] staging: rtl8192u: Fixed switch and case indentation error " sanjeev sharma
2014-07-09 6:04 ` [PATCH v2 4/4] staging: rtl8192u: Fixed too long lines " sanjeev sharma
2014-07-09 12:19 ` [PATCH v3 0/4] line wrapping of changelog sanjeev sharma
2014-07-09 12:15 ` Dan Carpenter
2014-07-09 12:19 ` [PATCH v3 1/4] staging: rtl8192u: Remove useless return statements sanjeev sharma
2014-07-09 19:24 ` Greg KH
2014-07-10 12:19 ` Sharma, Sanjeev
2014-07-09 12:19 ` [PATCH v3 2/4] staging: rtl8192u: Removed unnecessary whitespace & tab warning sanjeev sharma
2014-07-09 12:19 ` [PATCH v3 3/4] staging: rtl8192u: Fixed switch and case indentation error sanjeev sharma
2014-07-09 12:19 ` [PATCH v3 4/4] staging: rtl8192u: Fixed too long lines sanjeev sharma
2014-07-09 12:56 ` Joe Perches [this message]
2014-07-10 12:18 ` Sharma, Sanjeev
2014-07-10 12:24 ` [PATCH v4 0/4] staging: rtl8192u: checkpatch fixes sanjeev sharma
2014-07-10 12:24 ` [PATCH v4 1/4] staging: rtl8192u: Remove useless return statement sanjeev sharma
2014-07-10 12:24 ` [PATCH v4 2/4] staging: rtl8192u: Removed unnecessary whitespace & tab warning sanjeev sharma
2014-07-10 22:15 ` Greg KH
2014-07-10 12:24 ` [PATCH v4 3/4] staging: rtl8192u: Fixed switch and case indentation error sanjeev sharma
2014-07-10 12:24 ` [PATCH v4 4/4] staging: rtl8192u: Fixed too long line sanjeev sharma
2014-07-10 22:16 ` Greg KH
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=1404910612.932.95.camel@joe-AO725 \
--to=joe@perches.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.senna@gmail.com \
--cc=rmfrfs@gmail.com \
--cc=sanjeev_sharma@mentor.com \
--cc=sanjeevsharmaengg@gmail.com \
--cc=teobaluta@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
all inboxes | Powered by JetHome®