From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [MXS MMC 2/5] Some cleanups for the MMC driver
Date: Wed, 7 Dec 2011 13:50:29 +0100 [thread overview]
Message-ID: <20111207125029.GJ4585@pengutronix.de> (raw)
In-Reply-To: <20191.21688.696997.76000@ipc1.ka-ro>
On Wed, Dec 07, 2011 at 12:57:44PM +0100, Lothar Wa?mann wrote:
> Hi,
>
> Shawn Guo writes:
> > I'm fine with this cosmetic patch with the comments below addressed.
> >
> > On Tue, Dec 06, 2011 at 02:41:27PM +0100, Lothar Wa?mann wrote:
> > > - Remove bogus parens around numerical arguments in #define's
> > > - When defining bit masks, use the #def for the shift count
> > > instead of repeating the numbers
> >
> > This change brings a few 'line over 80 characters' checkpatch warnings.
> >
> will fix.
>
> > > - Remove bogus whitespace in indentation
> > > - Remove 'break' at end of switch statement
> > >
> > > Signed-off-by: Lothar Wa?mann <LW@KARO-electronics.de>
> > > ---
> > > drivers/mmc/host/mxs-mmc.c | 57 +++++++++++++++++++++----------------------
> > > 1 files changed, 28 insertions(+), 29 deletions(-)
> > >
> > > diff --git a/drivers/mmc/host/mxs-mmc.c b/drivers/mmc/host/mxs-mmc.c
> > [...]
> > > @@ -277,7 +277,7 @@ static irqreturn_t mxs_mmc_irq_handler(int irq, void *dev_id)
> > >
> > > stat = readl(host->base + HW_SSP_CTRL1);
> > > writel(stat & MXS_MMC_IRQ_BITS,
> > > - host->base + HW_SSP_CTRL1 + MXS_CLR_ADDR);
> >
> > This is an intended indentation with 7 spaces.
> >
> According to Documentation/CodingStyle spaces are never used for
> indentation (except in documentation, Kconfig and comments).
AFAIK "don't use spaces" only applies to the first line of a statement.
When breaking long lines using spaces to align to the containing
parenthesis is quite common (though I don't like it personally).
The rule for follow-up lines is only: Descendants are always
substantially shorter than the parent and are placed substantially to
the right.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2011-12-07 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 13:41 [MXS MMC 0/5] Some cleanups and fixes for the MXS MMC subsystem Lothar Waßmann
[not found] ` <e668bb1ab5fbe406ef604a18f59292a05149ae51.1323177907.git.LW@KARO-electronics.de>
2011-12-06 19:10 ` [MXS MMC 3/5] Add support for SSP/MMC ports 2 & 3 Wolfram Sang
2011-12-07 12:30 ` Shawn Guo
[not found] ` <b4779523002ceef3e95887bbcf7ed570cdd93a95.1323177907.git.LW@KARO-electronics.de>
2011-12-06 19:12 ` [MXS MMC 4/5] Check the return codes of clk_enable() and mxs_reset_block() Wolfram Sang
2011-12-07 12:33 ` Shawn Guo
[not found] ` <b1c45bfdbc9323b2a6c50ce213a3e895aeea2b2f.1323177907.git.LW@KARO-electronics.de>
2011-12-06 19:12 ` [MXS MMC 5/5] Add an appropriate MODULE_ALIAS Wolfram Sang
2011-12-07 12:34 ` Shawn Guo
[not found] ` <1ebaeb7f7ed88b1d82f5fc3a01c0661f38e2a16d.1323177907.git.LW@KARO-electronics.de>
2011-12-06 19:05 ` [MXS MMC 1/5] Fix grammatical error in comment Wolfram Sang
2011-12-07 11:00 ` Shawn Guo
[not found] ` <d935557e044d2ebc56b4e70487b519fe722e9017.1323177907.git.LW@KARO-electronics.de>
2011-12-07 12:01 ` [MXS MMC 2/5] Some cleanups for the MMC driver Shawn Guo
2011-12-07 11:57 ` Lothar Waßmann
2011-12-07 12:16 ` Shawn Guo
2011-12-07 12:50 ` Uwe Kleine-König [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=20111207125029.GJ4585@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 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).