public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Sheetal Tigadoli <sheetal.tigadoli@gmail.com>
To: chris@printf.net
Cc: joe@perches.com, linux-mmc@vger.kernel.org, ben@decadent.org.uk,
	kuninori.morimoto.gx@renesas.com, ulf.hansson@linaro.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] drivers; mmc: card:
Date: Mon,  2 Feb 2015 01:36:57 +0530	[thread overview]
Message-ID: <1422821222-24079-1-git-send-email-sheetal.tigadoli@gmail.com> (raw)

The patches, fix some coding style err/warnings from file block.c

./scripts/checkpatch.pl  --file --terse drivers/mmc/card/block.c
drivers/mmc/card/block.c:45: WARNING: Use #include <linux/uaccess.h> instead of <asm/uaccess.h>
drivers/mmc/card/block.c:102: WARNING: line over 80 characters
drivers/mmc/card/block.c:186: WARNING: Missing a blank line after declarations
drivers/mmc/card/block.c:238: WARNING: line over 80 characters
drivers/mmc/card/block.c:251: WARNING: line over 80 characters
drivers/mmc/card/block.c:279: WARNING: simple_strtoul is obsolete, use kstrtoul instead
drivers/mmc/card/block.c:280: WARNING: Missing a blank line after declarations
drivers/mmc/card/block.c:578: WARNING: line over 80 characters
drivers/mmc/card/block.c:586: WARNING: line over 80 characters
drivers/mmc/card/block.c:620: WARNING: Missing a blank line after declarations
drivers/mmc/card/block.c:1209: WARNING: line over 80 characters
drivers/mmc/card/block.c:1333: WARNING: quoted string split across lines
drivers/mmc/card/block.c:1720: WARNING: Missing a blank line after declarations
drivers/mmc/card/block.c:1734: WARNING: braces {} are not necessary for single statement blocks
drivers/mmc/card/block.c:1881: WARNING: else is not generally useful after a break or return
drivers/mmc/card/block.c:2019: WARNING: braces {} are not necessary for single statement blocks
drivers/mmc/card/block.c:2226: WARNING: line over 80 characters
drivers/mmc/card/block.c:2285: WARNING: line over 80 characters
drivers/mmc/card/block.c:2362: ERROR: that open brace { should be on the previous line
    total: 1 errors, 18 warnings, 2587 lines checked


             reply	other threads:[~2015-02-01 20:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 20:06 Sheetal Tigadoli [this message]
2015-02-01 20:06 ` [PATCH 1/5] drivers: mmc: card: Fix replaces simple_strtoul func call with kstrtoul Sheetal Tigadoli
2015-02-01 20:06   ` [PATCH 2/5] drivers: mmc: card: Fixes Missing blank line after variable initialization, coding style warning Sheetal Tigadoli
2015-02-01 20:07     ` [PATCH 3/5] drivers: mmc: card: Fixes WARNING braces are not necessary for single statement Sheetal Tigadoli
2015-02-01 20:07       ` [PATCH 4/5] drivers: mmc: card: Fixed ERROR that open brace should be on the previous line Sheetal Tigadoli
2015-02-01 20:07         ` [PATCH 5/5] drivers: mmc: card: Fixed warning line over 80 characters in file block Sheetal Tigadoli
2015-02-01 20:20     ` [PATCH 2/5] drivers: mmc: card: Fixes Missing blank line after variable initialization, coding style warning 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=1422821222-24079-1-git-send-email-sheetal.tigadoli@gmail.com \
    --to=sheetal.tigadoli@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=chris@printf.net \
    --cc=joe@perches.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@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