From: Chandan Babu R <chandanrlinux@gmail.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 1/5] xfs: fix silly whitespace problems with kernel libxfs
Date: Fri, 06 Aug 2021 11:15:02 +0530 [thread overview]
Message-ID: <877dgzjfde.fsf@garuda> (raw)
In-Reply-To: <162814684894.2777088.8991564362005574305.stgit@magnolia>
On 05 Aug 2021 at 00:00, "Darrick J. Wong" <djwong@kernel.org> wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> Fix a few whitespace errors such as spaces at the end of the line, etc.
> This gets us back to something more closely resembling parity.
>
Looks good to me.
Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
> fs/xfs/libxfs/xfs_attr_leaf.c | 2 +-
> fs/xfs/libxfs/xfs_format.h | 2 +-
> fs/xfs/libxfs/xfs_ialloc.c | 2 +-
> fs/xfs/libxfs/xfs_rmap_btree.h | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
>
>
> diff --git a/fs/xfs/libxfs/xfs_attr_leaf.c b/fs/xfs/libxfs/xfs_attr_leaf.c
> index b910bd209949..b277e0511cdd 100644
> --- a/fs/xfs/libxfs/xfs_attr_leaf.c
> +++ b/fs/xfs/libxfs/xfs_attr_leaf.c
> @@ -576,7 +576,7 @@ xfs_attr_shortform_bytesfit(
> switch (dp->i_df.if_format) {
> case XFS_DINODE_FMT_EXTENTS:
> /*
> - * If there is no attr fork and the data fork is extents,
> + * If there is no attr fork and the data fork is extents,
> * determine if creating the default attr fork will result
> * in the extents form migrating to btree. If so, the
> * minimum offset only needs to be the space required for
> diff --git a/fs/xfs/libxfs/xfs_format.h b/fs/xfs/libxfs/xfs_format.h
> index 76e2461b9e66..37570cf0537e 100644
> --- a/fs/xfs/libxfs/xfs_format.h
> +++ b/fs/xfs/libxfs/xfs_format.h
> @@ -9,7 +9,7 @@
> /*
> * XFS On Disk Format Definitions
> *
> - * This header file defines all the on-disk format definitions for
> + * This header file defines all the on-disk format definitions for
> * general XFS objects. Directory and attribute related objects are defined in
> * xfs_da_format.h, which log and log item formats are defined in
> * xfs_log_format.h. Everything else goes here.
> diff --git a/fs/xfs/libxfs/xfs_ialloc.c b/fs/xfs/libxfs/xfs_ialloc.c
> index aaf8805a82df..19eb7ec0103f 100644
> --- a/fs/xfs/libxfs/xfs_ialloc.c
> +++ b/fs/xfs/libxfs/xfs_ialloc.c
> @@ -1994,7 +1994,7 @@ xfs_difree_inobt(
> goto error0;
> }
>
> - /*
> + /*
> * Change the inode free counts and log the ag/sb changes.
> */
> be32_add_cpu(&agi->agi_freecount, 1);
> diff --git a/fs/xfs/libxfs/xfs_rmap_btree.h b/fs/xfs/libxfs/xfs_rmap_btree.h
> index 88d8d18788a2..f2eee6572af4 100644
> --- a/fs/xfs/libxfs/xfs_rmap_btree.h
> +++ b/fs/xfs/libxfs/xfs_rmap_btree.h
> @@ -59,4 +59,4 @@ extern xfs_extlen_t xfs_rmapbt_max_size(struct xfs_mount *mp,
> extern int xfs_rmapbt_calc_reserves(struct xfs_mount *mp, struct xfs_trans *tp,
> struct xfs_perag *pag, xfs_extlen_t *ask, xfs_extlen_t *used);
>
> -#endif /* __XFS_RMAP_BTREE_H__ */
> +#endif /* __XFS_RMAP_BTREE_H__ */
--
chandan
next prev parent reply other threads:[~2021-08-06 7:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 7:00 [PATCHSET 0/5] xfs: other stuff for 5.15 Darrick J. Wong
2021-08-05 7:00 ` [PATCH 1/5] xfs: fix silly whitespace problems with kernel libxfs Darrick J. Wong
2021-08-06 5:45 ` Chandan Babu R [this message]
2021-08-09 14:51 ` Christoph Hellwig
2021-08-05 7:00 ` [PATCH 2/5] xfs: drop experimental warnings for bigtime and inobtcount Darrick J. Wong
2021-08-06 5:51 ` Chandan Babu R
2021-08-09 14:53 ` Christoph Hellwig
2021-08-05 7:01 ` [PATCH 3/5] xfs: automatic resource cleanup of for_each_perag* Darrick J. Wong
2021-08-06 7:15 ` Chandan Babu R
2021-08-09 15:07 ` Christoph Hellwig
2021-08-05 7:01 ` [PATCH 4/5] xfs: grab active perag ref when reading AG headers Darrick J. Wong
2021-08-06 11:25 ` Chandan Babu R
2021-08-05 7:01 ` [PATCH 5/5] xfs: dump log intent items that cannot be recovered due to corruption Darrick J. Wong
2021-08-06 11:41 ` Chandan Babu R
2021-08-09 14:55 ` Christoph Hellwig
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=877dgzjfde.fsf@garuda \
--to=chandanrlinux@gmail.com \
--cc=djwong@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).