mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philippe Loctaux <phil@philippeloctaux.com>
To: clm@fb.com
Cc: jbacik@fb.com, dsterba@suse.com, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Philippe Loctaux <phil@philippeloctaux.com>
Subject: [PATCH] Btrfs: check-integrity: fixed comment blocks coding style issues
Date: Mon, 22 Feb 2016 00:02:47 +0100	[thread overview]
Message-ID: <1456095767-1561-1-git-send-email-phil@philippeloctaux.com> (raw)

Makes the comment blocks start with /* on separate lines, and end
with */ on separate lines as well.

Signed-off-by: Philippe Loctaux <phil@philippeloctaux.com>
---
 fs/btrfs/check-integrity.c | 30 ++++++++++++++++++++++--------
 1 file changed, 22 insertions(+), 8 deletions(-)

diff --git a/fs/btrfs/check-integrity.c b/fs/btrfs/check-integrity.c
index 861d472..cb5dc04 100644
--- a/fs/btrfs/check-integrity.c
+++ b/fs/btrfs/check-integrity.c
@@ -2070,8 +2070,11 @@ again:
 				goto continue_loop;
 			}
 
-			/* this is getting ugly for the
-			 * include_extent_data case... */
+			/*
+			 * this is getting ugly for the
+			 * include_extent_data case...
+			 */
+
 			bytenr = 0;	/* unknown */
 		} else {
 			processed_len = state->metablock_size;
@@ -2180,8 +2183,11 @@ static void btrfsic_bio_end_io(struct bio *bp)
 	struct btrfsic_block *block = (struct btrfsic_block *)bp->bi_private;
 	int iodone_w_error;
 
-	/* mutex is not held! This is not save if IO is not yet completed
-	 * on umount */
+	/*
+	 * mutex is not held! This is not save if IO is not yet completed
+	 * on umount
+	 */
+
 	iodone_w_error = 0;
 	if (bp->bi_error)
 		iodone_w_error = 1;
@@ -2861,8 +2867,12 @@ int btrfsic_submit_bh(int rw, struct buffer_head *bh)
 		return submit_bh(rw, bh);
 
 	mutex_lock(&btrfsic_mutex);
-	/* since btrfsic_submit_bh() might also be called before
-	 * btrfsic_mount(), this might return NULL */
+
+	/*
+	 * since btrfsic_submit_bh() might also be called before
+	 * btrfsic_mount(), this might return NULL
+	 */
+
 	dev_state = btrfsic_dev_state_lookup(bh->b_bdev);
 
 	/* Only called to write the superblock (incl. FLUSH/FUA) */
@@ -2924,8 +2934,12 @@ static void __btrfsic_submit_bio(int rw, struct bio *bio)
 		return;
 
 	mutex_lock(&btrfsic_mutex);
-	/* since btrfsic_submit_bio() is also called before
-	 * btrfsic_mount(), this might return NULL */
+
+	/*
+	 * since btrfsic_submit_bio() is also called before
+	 * btrfsic_mount(), this might return NULL
+	 */
+
 	dev_state = btrfsic_dev_state_lookup(bio->bi_bdev);
 	if (NULL != dev_state &&
 	    (rw & WRITE) && NULL != bio->bi_io_vec) {
-- 
2.7.1

                 reply	other threads:[~2016-02-21 23:41 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=1456095767-1561-1-git-send-email-phil@philippeloctaux.com \
    --to=phil@philippeloctaux.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®