public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Tushar Behera <tushar.behera@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	cjb@laptop.org, patches@linaro.org
Subject: Re: [PATCH 0/8] Fix coding style in sdhci.c
Date: Mon, 12 Nov 2012 11:24:41 +0900	[thread overview]
Message-ID: <50A05DE9.8070907@samsung.com> (raw)
In-Reply-To: <1352461198-21941-1-git-send-email-tushar.behera@linaro.org>

Hi Tushar,

Could you make one patch? Why do you separate patches?

Best Regards,
Jaehoon Chung

On 11/09/2012 08:39 PM, Tushar Behera wrote:
> Documents/CodingStyle Chapter 3 recommends usage of braces for both
> if and else statements if any of the branches contains multiple
> statements.
> 
> Cleaning up drivers/mmc/host/sdhci.c for all these occurrences.
> 
> Tushar Behera (8):
>   mmc: sdhci: fix coding style in sdhci_calc_timeout
>   mmc: sdhci: fix coding style in sdhci_set_transfer_mode
>   mmc: sdhci: fix coding style in sdhci_finish_data
>   mmc: sdhci: fix coding style in sdhci_set_clock
>   mmc: sdhci: fix coding style in sdhci_do_set_ios
>   mmc: sdhci: fix coding style in sdhci_execute_tuning
>   mmc: sdhci: fix coding style in sdhci_data_irq
>   mmc: sdhci: fix coding style in sdhci_add_host
> 
>  drivers/mmc/host/sdhci.c |   58 +++++++++++++++++++++++++--------------------
>  1 files changed, 32 insertions(+), 26 deletions(-)
> 


  parent reply	other threads:[~2012-11-12  2:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 11:39 [PATCH 0/8] Fix coding style in sdhci.c Tushar Behera
2012-11-09 11:39 ` [PATCH 1/8] mmc: sdhci: fix coding style in sdhci_calc_timeout Tushar Behera
2012-11-09 11:39 ` [PATCH 2/8] mmc: sdhci: fix coding style in sdhci_set_transfer_mode Tushar Behera
2012-11-09 11:39 ` [PATCH 3/8] mmc: sdhci: fix coding style in sdhci_finish_data Tushar Behera
2012-11-09 11:39 ` [PATCH 4/8] mmc: sdhci: fix coding style in sdhci_set_clock Tushar Behera
2012-11-09 11:39 ` [PATCH 5/8] mmc: sdhci: fix coding style in sdhci_do_set_ios Tushar Behera
2012-11-09 11:39 ` [PATCH 6/8] mmc: sdhci: fix coding style in sdhci_execute_tuning Tushar Behera
2012-11-09 11:39 ` [PATCH 7/8] mmc: sdhci: fix coding style in sdhci_data_irq Tushar Behera
2012-11-09 11:39 ` [PATCH 8/8] mmc: sdhci: fix coding style in sdhci_add_host Tushar Behera
2012-11-12  2:24 ` Jaehoon Chung [this message]
2012-11-12  4:38   ` [PATCH 0/8] Fix coding style in sdhci.c Tushar Behera
2012-11-12  7:12     ` Chris Ball
2012-11-12  7:37       ` Tushar Behera
2012-11-12  7:54       ` Joe Perches

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=50A05DE9.8070907@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=cjb@laptop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=tushar.behera@linaro.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