Re: [PATCH 29/29] fsdax: don't require CONFIG_BLOCK

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

To: Christoph Hellwig <hch@xxxxxx>
Subject: Re: [PATCH 29/29] fsdax: don't require CONFIG_BLOCK
From: Dan Williams <dan.j.williams@xxxxxxxxx>
Date: Tue, 23 Nov 2021 19:52:11 -0800
Cc: Mike Snitzer <snitzer@xxxxxxxxxx>, Ira Weiny <ira.weiny@xxxxxxxxx>, device-mapper development <dm-devel@xxxxxxxxxx>, linux-xfs <linux-xfs@xxxxxxxxxxxxxxx>, Linux NVDIMM <nvdimm@xxxxxxxxxxxxxxx>, linux-s390 <linux-s390@xxxxxxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, linux-erofs@xxxxxxxxxxxxxxxx, linux-ext4 <linux-ext4@xxxxxxxxxxxxxxx>, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
In-reply-to: <20211109083309.584081-30-hch@lst.de>

On Tue, Nov 9, 2021 at 12:34 AM Christoph Hellwig <hch@xxxxxx> wrote:
>
> The file system DAX code now does not require the block code.  So allow
> building a kernel with fuse DAX but not block layer.

Looks good to me.

Reviewed-by: Dan Williams <dan.j.williams@xxxxxxxxx>

References:
- decouple DAX from block devices
  - From: Christoph Hellwig
- [PATCH 29/29] fsdax: don't require CONFIG_BLOCK
  - From: Christoph Hellwig

Prev by Date: Re: [PATCH 28/29] iomap: build the block based code conditionally
Next by Date: [PATCH] hugetlbfs: avoid overflow in hugetlbfs_fallocate
Previous by thread: Re: [PATCH 29/29] fsdax: don't require CONFIG_BLOCK
Next by thread: [PATCH 27/29] dax: fix up some of the block device related ifdefs
Index(es):
- Date
- Thread

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

Powered by Linux