From: vivek m <bitu.kv@gmail.com>
To: valdis.kletnieks@vt.edu
Cc: gregkh@linuxfoundation.org, linux-fsdevel@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
vivek m <bitu.kv@gmail.com>
Subject: [PATCH] Staging: exfat: fixed a long line coding style issue
Date: Thu, 27 Feb 2020 21:11:05 +0000 [thread overview]
Message-ID: <1582837865-2219-1-git-send-email-bitu.kv@gmail.com> (raw)
Fixed a coding style issue
Signed-off-by: Vivek M <bitu.kv@gmail.com>
---
drivers/staging/exfat/exfat_blkdev.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/exfat/exfat_blkdev.c b/drivers/staging/exfat/exfat_blkdev.c
index 0a3dc35..ddff019 100644
--- a/drivers/staging/exfat/exfat_blkdev.c
+++ b/drivers/staging/exfat/exfat_blkdev.c
@@ -30,8 +30,9 @@ void exfat_bdev_close(struct super_block *sb)
p_bd->opened = false;
}
-int exfat_bdev_read(struct super_block *sb, sector_t secno, struct buffer_head **bh,
- u32 num_secs, bool read)
+int exfat_bdev_read(struct super_block *sb, sector_t secno,
+ struct buffer_head **bh, u32 num_secs,
+ bool read)
{
struct bd_info_t *p_bd = &(EXFAT_SB(sb)->bd_info);
struct fs_info_t *p_fs = &(EXFAT_SB(sb)->fs_info);
@@ -65,7 +66,8 @@ int exfat_bdev_read(struct super_block *sb, sector_t secno, struct buffer_head *
return -EIO;
}
-int exfat_bdev_write(struct super_block *sb, sector_t secno, struct buffer_head *bh,
+int exfat_bdev_write(struct super_block *sb, sector_t secno,
+ struct buffer_head *bh,
u32 num_secs, bool sync)
{
s32 count;
--
2.7.4
reply other threads:[~2020-02-27 21:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1582837865-2219-1-git-send-email-bitu.kv@gmail.com \
--to=bitu.kv@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=valdis.kletnieks@vt.edu \
/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;
as well as URLs for NNTP newsgroup(s).