public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: [PATCH] xfsprogs: remove stray libxfs whitespace
Date: Fri, 15 Nov 2019 13:35:31 -0600	[thread overview]
Message-ID: <57d4cc5d-6ec5-6977-1903-17a285202d79@redhat.com> (raw)

Not quite sure how these crept in but now's as good a time as any
to remove stray newline deltas vs. the kernel code.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---

diff --git a/libxfs/xfs_fs.h b/libxfs/xfs_fs.h
index 5dba5fbc..6ca43c73 100644
--- a/libxfs/xfs_fs.h
+++ b/libxfs/xfs_fs.h
@@ -755,6 +755,7 @@ struct xfs_scrub_metadata {
 #  define XFS_XATTR_LIST_MAX 65536
 #endif
 
+
 /*
  * ioctl commands that are used by Linux filesystems
  */
@@ -825,7 +826,6 @@ struct xfs_scrub_metadata {
 #define XFS_IOC_FSGEOMETRY	     _IOR ('X', 126, struct xfs_fsop_geom)
 #define XFS_IOC_BULKSTAT	     _IOR ('X', 127, struct xfs_bulkstat_req)
 #define XFS_IOC_INUMBERS	     _IOR ('X', 128, struct xfs_inumbers_req)
-
 /*	XFS_IOC_GETFSUUID ---------- deprecated 140	 */
 
 /* reflink ioctls; these MUST match the btrfs ioctl definitions */
diff --git a/libxfs/xfs_inode_buf.c b/libxfs/xfs_inode_buf.c
index fbdce4d6..4859b739 100644
--- a/libxfs/xfs_inode_buf.c
+++ b/libxfs/xfs_inode_buf.c
@@ -15,6 +15,7 @@
 #include "xfs_ialloc.h"
 #include "xfs_dir2.h"
 
+
 /*
  * Check that none of the inode's in the buffer have a next
  * unlinked field of 0.
diff --git a/libxfs/xfs_trans_inode.c b/libxfs/xfs_trans_inode.c
index 3a09ee76..7fa0c184 100644
--- a/libxfs/xfs_trans_inode.c
+++ b/libxfs/xfs_trans_inode.c
@@ -11,6 +11,7 @@
 #include "xfs_inode.h"
 #include "xfs_trans.h"
 
+
 /*
  * Add a locked inode to the transaction.
  *


             reply	other threads:[~2019-11-15 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 19:35 Eric Sandeen [this message]
2019-11-15 19:38 ` [PATCH] xfsprogs: remove stray libxfs whitespace Darrick J. Wong

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=57d4cc5d-6ec5-6977-1903-17a285202d79@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-xfs@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