From: Joe Perches <joe@perches.com>
To: Sangho Yi <antiroot@gmail.com>
Cc: broonie@opensource.wolfsonmicro.com, cbow@mail.ru,
dwmw2@inradead.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 3/3] power: wm831x_power.c: Fixed indentation bug and whitespace errors
Date: Wed, 17 Oct 2012 08:39:43 -0700 [thread overview]
Message-ID: <1350488383.3072.46.camel@joe-AO722> (raw)
In-Reply-To: <1350486076-3784-3-git-send-email-antiroot@gmail.com>
On Thu, 2012-10-18 at 00:01 +0900, Sangho Yi wrote:
> I removed trailing whitespaces and removed unnecessary whitespaces and
> indentation tabs.
[]
> diff --git a/drivers/power/wm831x_power.c b/drivers/power/wm831x_power.c
[]
> @@ -632,9 +632,8 @@ static __devexit int wm831x_power_remove(struct platform_device *pdev)
> int irq, i;
>
> for (i = 0; i < ARRAY_SIZE(wm831x_bat_irqs); i++) {
> - irq = wm831x_irq(wm831x,
There is a trailing space here...
> - platform_get_irq_byname(pdev,
> - wm831x_bat_irqs[i]));
but there's nothing wrong with this.
> + irq = wm831x_irq(wm831x, platform_get_irq_byname(pdev,
> + wm831x_bat_irqs[i]));
ugh.
If you're really going to do these sorts of changes
just to minimize overall line length, please keep
arguments aligned on parentheses where appropriate.
Maybe use a temporary if you're really concerned about
overall line length.
for (i = 0; i < ARRAY_SIZE(wm831x_bat_irqs); i++) {
irq = platform_get_irq_byname(pdev, wm831x_bat_irqs[i]);
irq = wm831x_irq(wm831x, irq);
}
next prev parent reply other threads:[~2012-10-17 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 15:01 [PATCH 1/3] power: wm831x_power: Fixed indentation errors Sangho Yi
2012-10-17 15:01 ` [PATCH 2/3] power: wm831x_power.c: fixed const struct declaration warning Sangho Yi
2012-10-17 15:01 ` [PATCH 3/3] power: wm831x_power.c: Fixed indentation bug and whitespace errors Sangho Yi
2012-10-17 15:39 ` Joe Perches [this message]
2012-10-17 18:00 ` [PATCH] wm831x: Add and use a wm831x_irq_byname convenience function Joe Perches
2012-11-26 21:35 ` Grant Likely
2012-11-26 21:40 ` Mark Brown
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=1350488383.3072.46.camel@joe-AO722 \
--to=joe@perches.com \
--cc=antiroot@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cbow@mail.ru \
--cc=dwmw2@inradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).