From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: trivial@kernel.org, akpm@linux-foundation.org,
adobriyan@gmail.com, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH 1/8] trivial: coding style fixes
Date: Fri, 16 Oct 2009 16:46:01 +0200 [thread overview]
Message-ID: <4AD88729.3050209@s5r6.in-berlin.de> (raw)
In-Reply-To: <1255635840-5691-1-git-send-email-cascardo@holoscopio.com>
Thadeu Lima de Souza Cascardo wrote:
> --- a/drivers/mmc/card/sdio_uart.c
> +++ b/drivers/mmc/card/sdio_uart.c
[...]
> @@ -946,31 +948,31 @@ static int sdio_uart_proc_show(struct seq_file *m, void *v)
> seq_printf(m, "%d: uart:SDIO", i);
> if(capable(CAP_SYS_ADMIN)) {
> seq_printf(m, " tx:%d rx:%d",
> - port->icount.tx, port->icount.rx);
> + port->icount.tx, port->icount.rx);
> if (port->icount.frame)
> seq_printf(m, " fe:%d",
> - port->icount.frame);
> + port->icount.frame);
> if (port->icount.parity)
> seq_printf(m, " pe:%d",
> - port->icount.parity);
> + port->icount.parity);
> if (port->icount.brk)
> seq_printf(m, " brk:%d",
> - port->icount.brk);
> + port->icount.brk);
> if (port->icount.overrun)
> seq_printf(m, " oe:%d",
> - port->icount.overrun);
> + port->icount.overrun);
> if (port->icount.cts)
[...]
The style problem of the original code was not indentation, but depth of
indentation levels. Why not factor this cascade out to a
show_icount_fields() function?
Plus, I hope Jiri enhanced your changelog a bit before he committed it.
(I only looked at this patch because I was wondering what subsystem it
changed --- the patch title doesn't say it.)
--
Stefan Richter
-=====-==--= =-=- =----
http://arcgraph.de/sr/
next prev parent reply other threads:[~2009-10-16 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 19:44 [PATCH 1/8] trivial: coding style fixes Thadeu Lima de Souza Cascardo
2009-10-16 13:31 ` Jiri Kosina
2009-10-16 14:46 ` Stefan Richter [this message]
2009-10-16 17:47 ` Jiri Kosina
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=4AD88729.3050209@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cascardo@holoscopio.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=trivial@kernel.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