From: Chinmayi Shetty <chinmayishetty359@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Bio: Fixed the code indentation by using tabs
Date: Sat, 13 Mar 2021 22:06:35 +0530 [thread overview]
Message-ID: <20210313163635.hisfsmzoxaeoyf73@client-VirtualBox> (raw)
Fixed coding style issue
Signed-off-by: Chinmayi Shetty <chinmayishetty359@gmail.com>
---
block/bio.c | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/block/bio.c b/block/bio.c
index a1c4d2900c7a..7c1354f7065c 100644
--- a/block/bio.c
+++ b/block/bio.c
@@ -501,6 +501,7 @@ void zero_fill_bio_iter(struct bio *bio, struct bvec_iter start)
__bio_for_each_segment(bv, bio, iter, start) {
char *data = bvec_kmap_irq(&bv, &flags);
+
memset(data, 0, bv.bv_len);
flush_dcache_page(bv.bv_page);
bvec_kunmap_irq(data, &flags);
@@ -616,15 +617,15 @@ void bio_put(struct bio *bio)
EXPORT_SYMBOL(bio_put);
/**
- * __bio_clone_fast - clone a bio that shares the original bio's biovec
- * @bio: destination bio
- * @bio_src: bio to clone
+ * __bio_clone_fast - clone a bio that shares the original bio's biovec
+ * @bio: destination bio
+ * @bio_src: bio to clone
*
* Clone a &bio. Caller will own the returned bio, but not
* the actual data it points to. Reference count of returned
- * bio will be one.
+ * bio will be one.
*
- * Caller must ensure that @bio_src is not freed before @bio.
+ * Caller must ensure that @bio_src is not freed before @bio.
*/
void __bio_clone_fast(struct bio *bio, struct bio *bio_src)
{
@@ -657,7 +658,7 @@ EXPORT_SYMBOL(__bio_clone_fast);
* @gfp_mask: allocation priority
* @bs: bio_set to allocate from
*
- * Like __bio_clone_fast, only also allocates the returned bio
+ * Like __bio_clone_fast, only also allocates the returned bio
*/
struct bio *bio_clone_fast(struct bio *bio, gfp_t gfp_mask, struct bio_set *bs)
{
@@ -1009,7 +1010,7 @@ static int __bio_iov_iter_get_pages(struct bio *bio, struct iov_iter *iter)
put_page(page);
} else {
if (WARN_ON_ONCE(bio_full(bio, len)))
- return -EINVAL;
+ return -EINVAL;
__bio_add_page(bio, page, len, offset);
}
offset = 0;
--
2.25.1
reply other threads:[~2021-03-13 16:37 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=20210313163635.hisfsmzoxaeoyf73@client-VirtualBox \
--to=chinmayishetty359@gmail.com \
--cc=linux-kernel@vger.kernel.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