Re: [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page

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

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page
From: Christoph Hellwig <hch@xxxxxx>
Date: Tue, 18 Dec 2018 19:06:17 +0100
Cc: Christoph Hellwig <hch@xxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <37aec6a5-d846-eca1-1708-bf80ea63c463@sandeen.net>
User-agent: Mutt/1.5.17 (2007-11-01)

On Mon, Dec 17, 2018 at 05:45:10PM -0600, Eric Sandeen wrote:
> Then we should hard code "512" in iomap_page_create I guess.  Just need
> consistency.

Fine with me.

Follow-Ups:
- Re: [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page
  - From: Darrick J. Wong

References:
- [PATCH 0/3] iomap: 1 cleanup, 1 fix, 1 optimization
  - From: Eric Sandeen
- [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page
  - From: Eric Sandeen
- Re: [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page
  - From: Christoph Hellwig
- Re: [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page
  - From: Eric Sandeen

Prev by Date: Re: [PATCH 18/52] virtio-fs: Map cache using the values from the capabilities
Next by Date: Re: [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page
Previous by thread: Re: [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page
Next by thread: Re: [PATCH 1/3] iomap: use SECTOR_SIZE instead of 512 in iomap_page
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