public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 4/5] mmc: tmio: improve checkpatch cleanness
Date: Tue, 30 May 2017 21:58:52 +0200	[thread overview]
Message-ID: <20170530195852.7r63hmfbbrwae6kt@ninjato> (raw)
In-Reply-To: <1496148654-20386-5-git-send-email-horms+renesas@verge.net.au>

[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]

On Tue, May 30, 2017 at 02:50:53PM +0200, Simon Horman wrote:
> Trivial updates to improve checkpatch cleanness.
> 
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>

Wow, all of them! When I reviewed your DMA refactoring patches, I meant
to fix only the whitespace issues which were affecting your patches. But
okay, it is a good timing to fix all of those, because of the said DMA
refactoring work, the BSP patches won't fit anymore anyhow, so upporting
them will not become significantly harder.

And while I don't agree with all of checkpatch suggestions, this patch
increases code readability for sure. I guess, what I am saying is:

Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

and

Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

I moved big files around two SD cards attached simultaneously to two
card slots on my Renesas Lager (H2).

> -	if (host->chan_tx && (data->flags & MMC_DATA_WRITE) && !host->force_pio) {
> +	if (host->chan_tx && (data->flags & MMC_DATA_WRITE) &&
> +	    !host->force_pio) {
>  		u32 status = sd_ctrl_read16_and_16_as_32(host, CTL_STATUS);
>  		bool done = false;

Let me give just one example where I think the 80 char limit doesn't
help readability. But no need to fix IMO; as I said, most of the stuff
is really helpful.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-05-30 19:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30 12:50 [PATCH 0/5] mmc: tmio, renesas-sdhi: cleanups Simon Horman
2017-05-30 12:50 ` [PATCH 1/5] MAINTAINERS: Update files for TMIO/SDHI MMC driver Simon Horman
2017-05-30 19:31   ` Wolfram Sang
2017-05-30 12:50 ` [PATCH 2/5] mmc: tmio: use EXPORT_SYMBOL_GPL Simon Horman
2017-05-30 19:35   ` Wolfram Sang
2017-05-30 12:50 ` [PATCH 3/5] mmc: tmio, renesas-sdhi: update Renesas related copyrights Simon Horman
2017-05-30 19:37   ` Wolfram Sang
2017-05-30 12:50 ` [PATCH 4/5] mmc: tmio: improve checkpatch cleanness Simon Horman
2017-05-30 19:58   ` Wolfram Sang [this message]
2017-05-31 19:58     ` Simon Horman
2017-05-31 20:02   ` Simon Horman
2017-05-30 12:50 ` [PATCH 5/5] mmc: renesas-sdhi: " Simon Horman
2017-05-30 19:57   ` Wolfram Sang
2017-06-08 13:52 ` [PATCH 0/5] mmc: tmio, renesas-sdhi: cleanups Ulf Hansson

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=20170530195852.7r63hmfbbrwae6kt@ninjato \
    --to=wsa@the-dreams.de \
    --cc=horms+renesas@verge.net.au \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=ulf.hansson@linaro.org \
    --cc=wsa+renesas@sang-engineering.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