All of lore.kernel.org
 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] btrfs: backref: Fixed checkpatch warning of over 80 characters
Date: Sat, 20 Feb 2016 12:16:14 -0600	[thread overview]
Message-ID: <1455992174-9121-1-git-send-email-tsimonq2@ubuntu.com> (raw)

checkpatch.pl reported a warning of over 80 characters on line 1833

Fixed by splitting up into multiple lines, no build errors afterwards
---
 fs/btrfs/backref.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c
index f6dac40..d097777 100644
--- a/fs/btrfs/backref.c
+++ b/fs/btrfs/backref.c
@@ -1830,7 +1830,11 @@ static int iterate_inode_extrefs(u64 inum, struct btrfs_root *fs_root,
 	unsigned long ptr;
 
 	while (1) {
-		ret = btrfs_find_one_extref(fs_root, inum, offset, path, &extref,
+		ret = btrfs_find_one_extref(fs_root,
+						inum,
+						offset,
+						path,
+						&extref,
 					    &offset);
 		if (ret < 0)
 			break;
-- 
2.7.0


             reply	other threads:[~2016-02-20 18:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 18:16 Simon Quigley [this message]
2016-02-20 18:17 [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters Simon Quigley
2016-02-21  0:02 ` Joe Perches
2016-02-21  2:06 ` Simon Quigley
2016-02-21  2:08   ` Simon Quigley
2016-02-22 11:57 ` David Sterba
2016-02-22 12:10   ` Simon Quigley
2016-02-22 12:33     ` David Sterba
2016-02-22 12:36       ` 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=1455992174-9121-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.