public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: 'Dan Carpenter' <dan.carpenter@oracle.com>,
	'David Woodhouse' <dwmw2@infradead.org>
Cc: 'Jingoo Han' <jg1.han@samsung.com>,
	kernel-janitors@vger.kernel.org,
	'Brian Norris' <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org
Subject: Re: [patch] mtd: cfi: indent some if statements
Date: Wed, 14 May 2014 23:08:25 +0000	[thread overview]
Message-ID: <005301cf6fc9$69236270$3b6a2750$%han@samsung.com> (raw)
In-Reply-To: <20140514141900.GB18082@mwanda>

On Wednesday, May 14, 2014 11:19 PM, Dan Carpenter wrote:
> 
> The break statements should be indented another tab.
> 
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Reviewed-by: Jingoo Han <jg1.han@samsung.com>

Best regards,
Jingoo Han

> 
> diff --git a/drivers/mtd/chips/cfi_cmdset_0020.c b/drivers/mtd/chips/cfi_cmdset_0020.c
> index 6293855..423666b 100644
> --- a/drivers/mtd/chips/cfi_cmdset_0020.c
> +++ b/drivers/mtd/chips/cfi_cmdset_0020.c
> @@ -961,7 +961,7 @@ static int cfi_staa_erase_varsize(struct mtd_info *mtd,
>  			chipnum++;
> 
>  			if (chipnum >= cfi->numchips)
> -			break;
> +				break;
>  		}
>  	}
> 
> @@ -1170,7 +1170,7 @@ static int cfi_staa_lock(struct mtd_info *mtd, loff_t ofs, uint64_t len)
>  			chipnum++;
> 
>  			if (chipnum >= cfi->numchips)
> -			break;
> +				break;
>  		}
>  	}
>  	return 0;
> diff --git a/drivers/mtd/chips/cfi_util.c b/drivers/mtd/chips/cfi_util.c
> index 08049f6..09c79bd 100644
> --- a/drivers/mtd/chips/cfi_util.c
> +++ b/drivers/mtd/chips/cfi_util.c
> @@ -239,7 +239,7 @@ int cfi_varsize_frob(struct mtd_info *mtd, varsize_frob_t frob,
>  			chipnum++;
> 
>  			if (chipnum >= cfi->numchips)
> -			break;
> +				break;
>  		}
>  	}
> 


  reply	other threads:[~2014-05-14 23:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 14:19 [patch] mtd: cfi: indent some if statements Dan Carpenter
2014-05-14 23:08 ` Jingoo Han [this message]
2014-05-21  0:38 ` Brian Norris

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='005301cf6fc9$69236270$3b6a2750$%han@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=computersforpeace@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dwmw2@infradead.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-mtd@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