The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: Chen Ni <nichen@iscas.ac.cn>
Cc: linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: Convert comma to semicolon
Date: Tue, 10 Mar 2026 09:52:15 +0100	[thread overview]
Message-ID: <aa_Z9AkLoS6BrTwc@nidhogg.toxiclabs.cc> (raw)
In-Reply-To: <20260306014800.1257769-1-nichen@iscas.ac.cn>

On Fri, Mar 06, 2026 at 09:48:00AM +0800, Chen Ni wrote:
> Using a ',' in place of a ';' can have unintended side effects.
> Although that is not the case here, it seems best to use ';'
> unless ',' is intended.
> 
> Found by inspection.
> No functional change intended.
> Compile tested only.

What tree HEAD did you apply this on?

I can't find where this code exists. I'm assuming you sent it against
some tree other than XFS's tree?

> 
> Signed-off-by: Chen Ni <nichen@iscas.ac.cn>
> ---
>  fs/xfs/xfs_aops.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/xfs/xfs_aops.c b/fs/xfs/xfs_aops.c
> index f279055fcea0..79ec98c8f299 100644
> --- a/fs/xfs/xfs_aops.c
> +++ b/fs/xfs/xfs_aops.c
> @@ -792,7 +792,7 @@ xfs_vm_readahead(
>  {
>  	struct iomap_read_folio_ctx	ctx = { .rac = rac };
>  
> -	ctx.ops = xfs_get_iomap_read_ops(rac->mapping),
> +	ctx.ops = xfs_get_iomap_read_ops(rac->mapping);
>  	iomap_readahead(&xfs_read_iomap_ops, &ctx, NULL);
>  }
>  
> -- 
> 2.25.1
> 
> 

  parent reply	other threads:[~2026-03-10  8:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06  1:48 [PATCH] xfs: Convert comma to semicolon Chen Ni
2026-03-06  8:41 ` Carlos Maiolino
2026-03-06  8:48 ` Joarder, Souptick
2026-03-10  8:52 ` Carlos Maiolino [this message]
2026-03-11  8:08   ` Chen Ni
  -- strict thread matches above, loose matches on Subject: below --
2024-09-03  7:39 [PATCH] xfs: convert " Chen Ni
2024-09-16 16:56 ` Darrick J. Wong
2024-07-16  8:01 Chen Ni
2024-07-18 15:27 ` Darrick J. Wong
2024-07-09  7:36 Chen Ni
2024-07-09 10:01 ` Dave Chinner
2024-07-09 21:57 ` Darrick J. Wong
2024-07-12 17:40 ` Chaitanya Kulkarni

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=aa_Z9AkLoS6BrTwc@nidhogg.toxiclabs.cc \
    --to=cem@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=nichen@iscas.ac.cn \
    /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