Re: [PATCH 06/10] iomap: Remove length and start fields from iomap_fiemap

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

To: Carlos Maiolino <cmaiolino@xxxxxxxxxx>
Subject: Re: [PATCH 06/10] iomap: Remove length and start fields from iomap_fiemap
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 14 Jan 2019 17:51:16 +0100
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, hch@xxxxxx, adilger@xxxxxxxxx, sandeen@xxxxxxxxxx, david@xxxxxxxxxxxxx
In-reply-to: <20181205091728.29903-7-cmaiolino@redhat.com>
User-agent: Mutt/1.5.17 (2007-11-01)

On Wed, Dec 05, 2018 at 10:17:24AM +0100, Carlos Maiolino wrote:
> fiemap_extent_info now embeds start and length parameters, users of
> iomap_fiemap() doesn't need to pass it individually anymore.
> 
> Signed-off-by: Carlos Maiolino <cmaiolino@xxxxxxxxxx>

Looks good,

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH 00/10 V2] New ->fiemap infrastructure and ->bmap removal
  - From: Carlos Maiolino
- [PATCH 06/10] iomap: Remove length and start fields from iomap_fiemap
  - From: Carlos Maiolino

Prev by Date: Re: [PATCH 05/10] fs: Move start and length fiemap fields into fiemap_extent_info
Next by Date: Re: [PATCH 07/10] fs: Use a void pointer to store fiemap_extent
Previous by thread: [PATCH 06/10] iomap: Remove length and start fields from iomap_fiemap
Next by thread: [PATCH 07/10] fs: Use a void pointer to store fiemap_extent
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]

Powered by Linux