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 1/3] btrfs: backref: String formatting fixes
Date: Sat, 20 Feb 2016 19:31:12 -0600 [thread overview]
Message-ID: <1456018274-7847-1-git-send-email-tsimonq2@ubuntu.com> (raw)
Checkpatch warns about a multi-line string
This fixes that issue and seperates the variables to another line
Signed-off-by: Simon Quigley <tsimonq2@ubuntu.com>
---
fs/btrfs/backref.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c
index 956fffa..a2c0595 100644
--- a/fs/btrfs/backref.c
+++ b/fs/btrfs/backref.c
@@ -1795,9 +1795,9 @@ static int iterate_inode_refs(u64 inum, struct btrfs_root *fs_root,
for (cur = 0; cur < btrfs_item_size(eb, item); cur += len) {
name_len = btrfs_inode_ref_name_len(eb, iref);
/* path must be released before calling iterate()! */
- pr_debug("following ref at offset %u for inode %llu in "
- "tree %llu\n", cur, found_key.objectid,
- fs_root->objectid);
+ pr_debug("following ref at offset %u for inode %llu in tree %llu\n",
+ cur, found_key.objectid,
+ fs_root->objectid);
ret = iterate(parent, name_len,
(unsigned long)(iref + 1), eb, ctx);
if (ret)
--
2.7.0
next 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 Simon Quigley [this message]
2016-02-21 1:31 ` [PATCH 2/3] btrfs: backref: Fixed string formatting error Simon Quigley
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-1-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).