From: Mike Snitzer <snitzer@redhat.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kbuild test robot <lkp@intel.com>,
linux-nvdimm@lists.01.org, Michael Ellerman <mpe@ellerman.id.au>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
dm-devel@redhat.com, Paul Mackerras <paulus@samba.org>,
Alasdair Kergon <agk@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
Gerald Schaefer <gerald.schaefer@de.ibm.com>
Subject: Re: [PATCH v6 0/2] dax, dm: stop requiring dax for device-mapper
Date: Thu, 4 Jan 2018 13:12:03 -0500 [thread overview]
Message-ID: <20180104181202.GA14491@redhat.com> (raw)
In-Reply-To: <151198199487.7051.7083189934624068090.stgit@dwillia2-desk3.amr.corp.intel.com>
On Wed, Nov 29 2017 at 1:59pm -0500,
Dan Williams <dan.j.williams@intel.com> wrote:
> Changes since v5 [1]:
> * Make DAX_DRIVER select DAX to simplify the Kconfig dependencies
> (Michael)
> * Rebase on 4.15-rc1 and add new IS_ENABLED(CONFIG_DAX_DRIVER) checks in
> drivers/md/dm-log-writes.c.
>
> [1]: https://lists.01.org/pipermail/linux-nvdimm/2017-September/012569.html
>
> ---
>
> Hi Mike,
>
> Bart points out that the DAX core is unconditionally enabled if
> device-mapper is enabled. Add some config machinery and some
> stub/static-inline routines to allow dax infrastructure to be deleted
> from device-mapper at compile time.
Hey Dan,
Did you want me to pick this up for 4.16 or were you thinking of sending
the changes through a different tree?
I'm fine with picking these up so long as you don't expect the dax.h and
Kconfig changes to become a source of conflict come merge time.
Let me know, thanks!
Mike
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-01-04 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 18:59 [PATCH v6 0/2] dax, dm: stop requiring dax for device-mapper Dan Williams
2017-11-29 19:00 ` [PATCH v6 1/2] dax: introduce CONFIG_DAX_DRIVER Dan Williams
2018-01-08 16:07 ` Mike Snitzer
2017-11-29 19:00 ` [PATCH v6 2/2] dm: allow device-mapper to operate without dax support Dan Williams
2018-01-08 16:08 ` Mike Snitzer
2018-01-04 18:12 ` Mike Snitzer [this message]
2018-01-07 20:31 ` [PATCH v6 0/2] dax, dm: stop requiring dax for device-mapper Dan Williams
2018-01-08 16:06 ` Mike Snitzer
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=20180104181202.GA14491@redhat.com \
--to=snitzer@redhat.com \
--cc=Bart.VanAssche@wdc.com \
--cc=agk@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=dan.j.williams@intel.com \
--cc=dm-devel@redhat.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-nvdimm@lists.01.org \
--cc=lkp@intel.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.com \
/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).