From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
linux-xfs@vger.kernel.org, nvdimm@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: dax_supported() related cleanups v2
Date: Wed, 22 Sep 2021 19:34:28 +0200 [thread overview]
Message-ID: <20210922173431.2454024-1-hch@lst.de> (raw)
Hi all,
this series first clarifies how to use fsdax in the Kconfig help a bit,
and then untangles the code path that checks if fsdax is supported.
Changes since v1:
- improve the FS_DAX Kconfig help text further
- write a proper commit log for a patch missing it
Diffstat
drivers/dax/super.c | 191 +++++++++++++++++++-------------------------------
drivers/md/dm-table.c | 9 --
drivers/md/dm.c | 2
fs/Kconfig | 21 ++++-
fs/ext2/super.c | 3
fs/ext4/super.c | 3
fs/xfs/xfs_super.c | 16 +++-
include/linux/dax.h | 41 +---------
8 files changed, 117 insertions(+), 169 deletions(-)
next reply other threads:[~2021-09-22 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 17:34 Christoph Hellwig [this message]
2021-09-22 17:34 ` [PATCH 1/3] nvdimm/pmem: fix creating the dax group Christoph Hellwig
2021-09-22 17:34 ` [PATCH 2/3] nvdimm/pmem: move dax_attribute_group from dax to pmem Christoph Hellwig
2021-09-22 17:34 ` [PATCH 3/3] block: warn if ->groups is set when calling add_disk Christoph Hellwig
2021-09-22 17:55 ` dax_supported() related cleanups v2 Dan Williams
2021-09-22 18:33 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2021-08-26 13:55 Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210922173431.2454024-1-hch@lst.de \
--to=hch@lst.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=snitzer@redhat.com \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).