public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: studentxswpy@163.com
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hacash Robot <hacashRobot@santino.com>
Subject: Re: [PATCH -next] xfs: delete extra space and tab in blank line
Date: Sun, 31 Jul 2022 09:23:08 -0700	[thread overview]
Message-ID: <YuasbFHWfWiXPUJM@magnolia> (raw)
In-Reply-To: <20220730092959.3103627-1-studentxswpy@163.com>

On Sat, Jul 30, 2022 at 05:29:59PM +0800, studentxswpy@163.com wrote:
> From: Xie Shaowen <studentxswpy@163.com>
> 
> delete extra space and tab in blank line, there is no functional change.
> 
> Reported-by: Hacash Robot <hacashRobot@santino.com>
> Signed-off-by: Xie Shaowen <studentxswpy@163.com>

The last hunk doesn't apply, but fmeh, whatever.
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  fs/xfs/xfs_extfree_item.c | 12 ++++++------
>  fs/xfs/xfs_log.c          |  4 ++--
>  2 files changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/fs/xfs/xfs_extfree_item.c b/fs/xfs/xfs_extfree_item.c
> index 765be054dffe..08b0c8b553fc 100644
> --- a/fs/xfs/xfs_extfree_item.c
> +++ b/fs/xfs/xfs_extfree_item.c
> @@ -187,12 +187,12 @@ xfs_efi_copy_format(xfs_log_iovec_t *buf, xfs_efi_log_format_t *dst_efi_fmt)
>  {
>  	xfs_efi_log_format_t *src_efi_fmt = buf->i_addr;
>  	uint i;
> -	uint len = sizeof(xfs_efi_log_format_t) + 
> -		(src_efi_fmt->efi_nextents - 1) * sizeof(xfs_extent_t);  
> -	uint len32 = sizeof(xfs_efi_log_format_32_t) + 
> -		(src_efi_fmt->efi_nextents - 1) * sizeof(xfs_extent_32_t);  
> -	uint len64 = sizeof(xfs_efi_log_format_64_t) + 
> -		(src_efi_fmt->efi_nextents - 1) * sizeof(xfs_extent_64_t);  
> +	uint len = sizeof(xfs_efi_log_format_t) +
> +		(src_efi_fmt->efi_nextents - 1) * sizeof(xfs_extent_t);
> +	uint len32 = sizeof(xfs_efi_log_format_32_t) +
> +		(src_efi_fmt->efi_nextents - 1) * sizeof(xfs_extent_32_t);
> +	uint len64 = sizeof(xfs_efi_log_format_64_t) +
> +		(src_efi_fmt->efi_nextents - 1) * sizeof(xfs_extent_64_t);
>  
>  	if (buf->i_len == len) {
>  		memcpy((char *)dst_efi_fmt, (char*)src_efi_fmt, len);
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index ae904b21e9cc..6f661fadb755 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -2000,7 +2000,7 @@ xlog_calc_iclog_size(
>  }
>  
>  /*
> - * Flush out the in-core log (iclog) to the on-disk log in an asynchronous 
> + * Flush out the in-core log (iclog) to the on-disk log in an asynchronous
>   * fashion.  Previously, we should have moved the current iclog
>   * ptr in the log to point to the next available iclog.  This allows further
>   * write to continue while this code syncs out an iclog ready to go.
> @@ -2042,7 +2042,7 @@ xlog_sync(
>  	xlog_grant_add_space(log, &log->l_write_head.grant, roundoff);
>  
>  	/* put cycle number in every block */
> -	xlog_pack_data(log, iclog, roundoff); 
> +	xlog_pack_data(log, iclog, roundoff);
>  
>  	/* real byte length */
>  	size = iclog->ic_offset;
> -- 
> 2.25.1
> 

      reply	other threads:[~2022-07-31 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30  9:29 [PATCH -next] xfs: delete extra space and tab in blank line studentxswpy
2022-07-31 16:23 ` Darrick J. Wong [this message]

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=YuasbFHWfWiXPUJM@magnolia \
    --to=djwong@kernel.org \
    --cc=hacashRobot@santino.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=studentxswpy@163.com \
    /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