Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper

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

To: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
Subject: Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 9 Oct 2019 00:07:45 -0700
Cc: Matthew Bobrowski <mbobrowski@xxxxxxxxxxxxxx>, tytso@xxxxxxx, jack@xxxxxxx, adilger.kernel@xxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, hch@xxxxxxxxxxxxx, david@xxxxxxxxxxxxx, darrick.wong@xxxxxxxxxx
In-reply-to: <20191009060255.8055742049@d06av24.portsmouth.uk.ibm.com>
User-agent: Mutt/1.12.1 (2019-06-15)

On Wed, Oct 09, 2019 at 11:32:54AM +0530, Ritesh Harjani wrote:
> We can also get rid of "first_block" argument here.

That would just duplicate filling it out in all callers, so why?

Follow-Ups:
- Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
  - From: Ritesh Harjani

References:
- [PATCH v4 0/8] ext4: port direct I/O to iomap infrastructure
  - From: Matthew Bobrowski
- [PATCH v4 1/8] ext4: move out iomap field population into separate helper
  - From: Matthew Bobrowski
- Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
  - From: Ritesh Harjani

Prev by Date: Re: [PATCH V2 00/26] mm, xfs: non-blocking inode reclaim
Next by Date: Re: [PATCH v4 8/8] ext4: introduce direct I/O write path using iomap infrastructure
Previous by thread: Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Next by thread: Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]