linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Quigley <tsimonq2@ubuntu.com>
To: clm@fb.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Simon Quigley <tsimonq2@ubuntu.com>
Subject: [PATCH 2/3] btrfs: backref: Fixed string formatting error
Date: Sat, 20 Feb 2016 19:31:13 -0600	[thread overview]
Message-ID: <1456018274-7847-2-git-send-email-tsimonq2@ubuntu.com> (raw)
In-Reply-To: <1456018274-7847-1-git-send-email-tsimonq2@ubuntu.com>

Checkpatch reported an error that there was a multi-line string.

This puts the string on one line and the variables on another.

Signed-off-by: Simon Quigley <tsimonq2@ubuntu.com>
---
 fs/btrfs/backref.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c
index a2c0595..632845a 100644
--- a/fs/btrfs/backref.c
+++ b/fs/btrfs/backref.c
@@ -1696,9 +1696,8 @@ int iterate_extent_inodes(struct btrfs_fs_info *fs_info,
 			break;
 		ULIST_ITER_INIT(&root_uiter);
 		while (!ret && (root_node = ulist_next(roots, &root_uiter))) {
-			pr_debug("root %llu references leaf %llu, data list "
-				 "%#llx\n", root_node->val, ref_node->val,
-				 ref_node->aux);
+			pr_debug("root %llu references leaf %llu, data list %#llx\n",
+				root_node->val, ref_node->val, ref_node->aux);
 			ret = iterate_leaf_refs((struct extent_inode_elem *)
 						(uintptr_t)ref_node->aux,
 						root_node->val,
-- 
2.7.0


  reply	other threads:[~2016-02-21  1:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-21  1:31 [PATCH 1/3] btrfs: backref: String formatting fixes Simon Quigley
2016-02-21  1:31 ` Simon Quigley [this message]
2016-02-21  1:31 ` [PATCH 3/3] btrfs: backref: Fixed string error generated by Checkpatch Simon Quigley

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=1456018274-7847-2-git-send-email-tsimonq2@ubuntu.com \
    --to=tsimonq2@ubuntu.com \
    --cc=clm@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;
as well as URLs for NNTP newsgroup(s).