Re: [RFCv3 02/10] libfs: Add __generic_file_fsync_nolock implementation

To: "Ritesh Harjani (IBM)" <ritesh.list@xxxxxxxxx>
Subject: Re: [RFCv3 02/10] libfs: Add __generic_file_fsync_nolock implementation
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 13 Apr 2023 22:59:24 -0700
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, Jan Kara <jack@xxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, "Darrick J . Wong" <djwong@xxxxxxxxxx>, Ojaswin Mujoo <ojaswin@xxxxxxxxxxxxx>, Disha Goel <disgoel@xxxxxxxxxxxxx>
In-reply-to: <e65768eb0fe145c803ba4afdc869a1757d51d758.1681365596.git.ritesh.list@gmail.com>
References: <cover.1681365596.git.ritesh.list@gmail.com> <e65768eb0fe145c803ba4afdc869a1757d51d758.1681365596.git.ritesh.list@gmail.com>

Still no fan of the naming and placement here.  This is specific
to the fs/buffer.c infrastructure.

Follow-Ups:
- Re: [RFCv3 02/10] libfs: Add __generic_file_fsync_nolock implementation
  - From: Jan Kara

References:
- [RFCv3 00/10] ext2: DIO to use iomap
  - From: Ritesh Harjani (IBM)
- [RFCv3 02/10] libfs: Add __generic_file_fsync_nolock implementation
  - From: Ritesh Harjani (IBM)