From: Sangho Yi <antiroot@gmail.com>
To: prakity@marvell.com, aaron.lu@amd.com, linus.walleij@linaro.org,
ulf.hansson@stericsson.com, cjb@laptop.org
Cc: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
Sangho Yi <antiroot@gmail.com>
Subject: [PATCH 1/3] drivers: mmc: core: sdio.c: fixed lines with > 80 chars
Date: Fri, 19 Oct 2012 01:06:32 +0900 [thread overview]
Message-ID: <1350576394-2008-1-git-send-email-antiroot@gmail.com> (raw)
In-Reply-To: <n>
Fixed coding style warning cases for exceeding 80 chars per line on
sdio.c.
Signed-off-by: Sangho Yi <antiroot@gmail.com>
---
drivers/mmc/core/sdio.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/core/sdio.c b/drivers/mmc/core/sdio.c
index 2273ce6..14326e8 100644
--- a/drivers/mmc/core/sdio.c
+++ b/drivers/mmc/core/sdio.c
@@ -47,7 +47,8 @@ static int sdio_read_fbr(struct sdio_func *func)
if (data == 0x0f) {
ret = mmc_io_rw_direct(func->card, 0, 0,
- SDIO_FBR_BASE(func->num) + SDIO_FBR_STD_IF_EXT, 0, &data);
+ SDIO_FBR_BASE(func->num) + SDIO_FBR_STD_IF_EXT,
+ 0, &data);
if (ret)
goto out;
}
@@ -619,7 +620,8 @@ static int mmc_sdio_init_card(struct mmc_host *host, u32 ocr,
card->type = MMC_TYPE_SD_COMBO;
if (oldcard && (oldcard->type != MMC_TYPE_SD_COMBO ||
- memcmp(card->raw_cid, oldcard->raw_cid, sizeof(card->raw_cid)) != 0)) {
+ memcmp(card->raw_cid, oldcard->raw_cid,
+ sizeof(card->raw_cid)) != 0)) {
mmc_remove_card(card);
return -ENOENT;
}
--
1.7.9.5
next reply other threads:[~2012-10-18 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 16:06 Sangho Yi [this message]
2012-10-18 16:06 ` [PATCH 2/3] drivers: mmc: core: sdio.c: fixed coding style error on for() statement Sangho Yi
2012-10-18 16:10 ` Philip Rakity
2012-10-18 16:06 ` [PATCH 3/3] drivers: mmc: core: sdio.c: fixed from pr_warning(... to pr_warn( Sangho Yi
-- strict thread matches above, loose matches on Subject: below --
2012-10-17 14:13 [PATCH 1/3] drivers: mmc: core: sdio.c: fixed lines with > 80 chars Sangho Yi
2012-10-17 19:35 ` Philip Rakity
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=1350576394-2008-1-git-send-email-antiroot@gmail.com \
--to=antiroot@gmail.com \
--cc=aaron.lu@amd.com \
--cc=cjb@laptop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=prakity@marvell.com \
--cc=ulf.hansson@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.