Re: [PATCH] xfs_io: copy_range can take up to 8 arguments

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH] xfs_io: copy_range can take up to 8 arguments
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 1 May 2020 01:07:30 -0700
Cc: linux-xfs <linux-xfs@xxxxxxxxxxxxxxx>
In-reply-to: <08c6de7b-4caf-1162-29e5-94d8dfe959d6@redhat.com>
References: <08c6de7b-4caf-1162-29e5-94d8dfe959d6@redhat.com>

On Thu, Apr 30, 2020 at 04:41:55PM -0500, Eric Sandeen wrote:
> If we use the "-f N" variant for the source file specification, we will
> have up to 8 total arguments.
> 
> Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx>

Looks good,

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH] xfs_io: copy_range can take up to 8 arguments
  - From: Eric Sandeen

Prev by Date: Re: [PATCH] xfs: pass a commit_mode to xfs_trans_commit
Next by Date: Re: [PATCH 01/21] xfs: refactor log recovery item sorting into a generic dispatch structure
Previous by thread: [PATCH] xfs_io: copy_range can take up to 8 arguments
Next by thread: [RFC PATCH V2 6/9] iomap: use attach/clear_page_private
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux