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 2/2] Btrfs: dev-replace: fixed comment blocks coding style issues
Date: Mon, 22 Feb 2016 01:27:36 +0100	[thread overview]
Message-ID: <1456100856-15604-2-git-send-email-phil@philippeloctaux.com> (raw)
In-Reply-To: <1456100856-15604-1-git-send-email-phil@philippeloctaux.com>

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/dev-replace.c | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c
index b89a8c6..0d817aa 100644
--- a/fs/btrfs/dev-replace.c
+++ b/fs/btrfs/dev-replace.c
@@ -650,8 +650,10 @@ void btrfs_dev_replace_status(struct btrfs_fs_info *fs_info,
 	struct btrfs_device *srcdev;
 
 	btrfs_dev_replace_lock(dev_replace);
-	/* even if !dev_replace_is_valid, the values are good enough for
-	 * the replace_status ioctl */
+	/*
+	 * even if !dev_replace_is_valid, the values are good enough for
+	 * the replace_status ioctl
+	 */
 	args->result = BTRFS_IOCTL_DEV_REPLACE_RESULT_NO_ERROR;
 	args->status.replace_state = dev_replace->replace_state;
 	args->status.time_started = dev_replace->time_started;
@@ -870,8 +872,10 @@ void btrfs_dev_replace_lock(struct btrfs_dev_replace *dev_replace)
 	/* the beginning is just an optimization for the typical case */
 	if (atomic_read(&dev_replace->nesting_level) == 0) {
 acquire_lock:
-		/* this is not a nested case where the same thread
-		 * is trying to acqurire the same lock twice */
+		/*
+		 * this is not a nested case where the same thread
+		 * is trying to acqurire the same lock twice
+		 */
 		mutex_lock(&dev_replace->lock);
 		mutex_lock(&dev_replace->lock_management_lock);
 		dev_replace->lock_owner = current->pid;
-- 
2.7.1

      reply	other threads:[~2016-02-22  0:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22  0:27 [PATCH 1/2] Btrfs: dev-replace: Fixed indentation " Philippe Loctaux
2016-02-22  0:27 ` Philippe Loctaux [this message]

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=1456100856-15604-2-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®