<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>e4b0925f - libnvdimm: Fix ACPI_NFIT in BLK_DEV_PMEM help</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#e4b0925f</link>
        <description>libnvdimm: Fix ACPI_NFIT in BLK_DEV_PMEM helpThe ACPI_NFIT config option is described incorrectly as theinverse NFIT_ACPI, which doesn&apos;t exist, so update the helpto the actual config option.Signed-off-by: Peter Robinson &lt;pbrobinson@gmail.com&gt;Link: https://lore.kernel.org/r/20240212123716.795996-1-pbrobinson@gmail.comSigned-off-by: Dave Jiang &lt;dave.jiang@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Mon, 12 Feb 2024 12:37:10 +0000</pubDate>
        <dc:creator>Peter Robinson &lt;pbrobinson@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>c91d7136 - nvdimm: Support sizeof(struct page) &gt; MAX_STRUCT_PAGE_SIZE</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#c91d7136</link>
        <description>nvdimm: Support sizeof(struct page) &gt; MAX_STRUCT_PAGE_SIZECommit 6e9f05dc66f9 (&quot;libnvdimm/pfn_dev: increase MAX_STRUCT_PAGE_SIZE&quot;)...updated MAX_STRUCT_PAGE_SIZE to account for sizeof(struct page)potentially doubling in the case of CONFIG_KMSAN=y. Unfortunately thisdoubles the amount of capacity stolen from user addressable capacity foreveryone, regardless of whether they are using the debug option. Revertthat change, mandate that MAX_STRUCT_PAGE_SIZE never exceed 64, butallow for debug scenarios to proceed with creating debug sized page mapswith a compile option to support debug scenarios.Note that this only applies to cases where the page map is permanent,i.e. stored in a reservation of the pmem itself (&quot;--map=dev&quot; in &quot;ndctlcreate-namespace&quot; terms). For the &quot;--map=mem&quot; case, since the allocationis ephemeral for the lifespan of the namespace, there are no explicitrestriction. However, the implicit restriction, of having enoughavailable &quot;System RAM&quot; to store the page map for the typically largepmem, still applies.Fixes: 6e9f05dc66f9 (&quot;libnvdimm/pfn_dev: increase MAX_STRUCT_PAGE_SIZE&quot;)Cc: &lt;stable@vger.kernel.org&gt;Cc: Alexander Potapenko &lt;glider@google.com&gt;Cc: Marco Elver &lt;elver@google.com&gt;Reported-by: Jeff Moyer &lt;jmoyer@redhat.com&gt;Acked-by: Yu Zhao &lt;yuzhao@google.com&gt;Link: https://lore.kernel.org/r/167467815773.463042.7022545814443036382.stgit@dwillia2-xfh.jf.intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Wed, 25 Jan 2023 20:23:46 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>15a83487 - libnvdimm: Introduce CONFIG_NVDIMM_SECURITY_TEST flag</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#15a83487</link>
        <description>libnvdimm: Introduce CONFIG_NVDIMM_SECURITY_TEST flagnfit_test overrode the security_show() sysfs attribute function in nvdimmdimm_devs in order to allow testing of security unlock. With theintroduction of CXL security commands, the trick to overridesecurity_show() becomes significantly more complicated. By introdcing asecurity flag CONFIG_NVDIMM_SECURITY_TEST, libnvdimm can just toggle thecheck via a compile option. In addition the original override can can beremoved from tools/testing/nvdimm/.The flag will also be used to bypass cpu_cache_invalidate_memregion() whenset in a different commit. This allows testing on QEMU with nfit_test orcxl_test since cpu_cache_has_invalidate_memregion() checks whetherX86_FEATURE_HYPERVISOR cpu feature flag is set on x86.Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Signed-off-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Link: https://lore.kernel.org/r/166983618758.2734609.18031639517065867138.stgit@djiang5-desk3.ch.intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Wed, 30 Nov 2022 19:23:07 +0000</pubDate>
        <dc:creator>Dave Jiang &lt;dave.jiang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f8669f1d - nvdimm/blk: Delete the block-aperture window driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#f8669f1d</link>
        <description>nvdimm/blk: Delete the block-aperture window driverBlock Aperture Window support was an attempt to layer an error modelover PMEM for platforms that did not support machine-check-recovery.However, it was abandoned before it ever shipped, and only ever existedin the ACPI specification. Meanwhile Linux has carried a large pile ofdead code for non-shipping infrastructure. For years it has been off tothe side out of the way, but now CXL and recent directions with DAXsupport have the potential to collide with this code.In preparation for adding discontiguous namespace support, apre-requisite for the nvdimm subsystem to replace device-mapper forstriping + concatenation use cases, delete BLK aperture support.On the obscure chance that some hardware vendor shipped support for thismode, note that the driver will still keep BLK space reserved in thelabel area. So an end user in this case would still have the opportunityto report the regression to get BLK-mode support restored withoutrisking the data they have on that device.Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Link: https://lore.kernel.org/r/164688416668.2879318.16903178375774275120.stgit@dwillia2-desk3.amr.corp.intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Thu, 10 Mar 2022 03:49:26 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>afd586f0 - dax: remove CONFIG_DAX_DRIVER</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#afd586f0</link>
        <description>dax: remove CONFIG_DAX_DRIVERCONFIG_DAX_DRIVER only selects CONFIG_DAX now, so remove it.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Link: https://lore.kernel.org/r/20211129102203.2243509-4-hch@lst.deSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Mon, 29 Nov 2021 10:21:37 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>33dd7075 - lib: Uplevel the pmem &quot;region&quot; ida to a global allocator</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#33dd7075</link>
        <description>lib: Uplevel the pmem &quot;region&quot; ida to a global allocatorIn preparation for handling platform differentiated memory types beyondpersistent memory, uplevel the &quot;region&quot; identifier to a global numberspace. This enables a device-dax instance to be registered to any memorytype with guaranteed unique names.Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Acked-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Thu, 07 Nov 2019 01:43:31 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>62974fc3 - libnvdimm: Enable unit test infrastructure compile checks</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#62974fc3</link>
        <description>libnvdimm: Enable unit test infrastructure compile checksThe infrastructure to mock core libnvdimm routines for unit testingpurposes is prone to bitrot relative to refactoring of that core.  Arrangefor the unit test core to be built when CONFIG_COMPILE_TEST=y.  This doesnot result in a functional unit test environment, it is only a helper for0day to catch unit test build regressions.Note that there are a few x86isms in the implementation, so this does notbother compile testing this architectures other than 64-bit x86.Link: https://lore.kernel.org/r/156763690875.2556198.15786177395425033830.stgit@dwillia2-desk3.amr.corp.intel.comReported-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Signed-off-by: Jason Gunthorpe &lt;jgg@mellanox.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Wed, 04 Sep 2019 22:43:31 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>ae4a0502 - docs: nvdimm: add it to the driver-api book</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#ae4a0502</link>
        <description>docs: nvdimm: add it to the driver-api bookThe descriptions here are from Kernel driver&apos;s PoV.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;Acked-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Tue, 18 Jun 2019 19:32:31 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b0a4aa95 - docs: nvdimm: convert to ReST</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#b0a4aa95</link>
        <description>docs: nvdimm: convert to ReSTRename the nvdimm documentation files to ReST, add anindex for them and adjust in order to produce a nice htmloutput via the Sphinx build system.At its new index.rst, let&apos;s add a :orphan: while this is not linked tothe main index.rst file, in order to avoid build warnings.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;Acked-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Thu, 18 Apr 2019 17:21:14 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#ec8f24b7</link>
        <description>treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is:  GPL-2.0-onlySigned-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>4c6926a2 - acpi/nfit, libnvdimm: Add unlock of nvdimm support for Intel DIMMs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#4c6926a2</link>
        <description>acpi/nfit, libnvdimm: Add unlock of nvdimm support for Intel DIMMsAdd support to unlock the dimm via the kernel key management APIs. Thepassphrase is expected to be pulled from userspace through keyutils.The key management and sysfs attributes are libnvdimm generic.Encrypted keys are used to protect the nvdimm passphrase at rest. Themaster key can be a trusted-key sealed in a TPM, preferred, or anencrypted-key, more flexible, but more exposure to a potential attacker.Signed-off-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Co-developed-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Reported-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Thu, 06 Dec 2018 20:40:01 +0000</pubDate>
        <dc:creator>Dave Jiang &lt;dave.jiang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f22acf82 - Revert &quot;libnvdimm, of_pmem: workaround OF_NUMA=n build error&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#f22acf82</link>
        <description>Revert &quot;libnvdimm, of_pmem: workaround OF_NUMA=n build error&quot;With commit df3f126482db (&quot;libnvdimm, of_pmem: use dev_to_node() insteadof of_node_to_nid()&quot;) it is now possible to allow of_pmem to be built asa module as originally implemented.Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Thu, 19 Apr 2018 22:07:42 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>291717b6 - libnvdimm, of_pmem: workaround OF_NUMA=n build error</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#291717b6</link>
        <description>libnvdimm, of_pmem: workaround OF_NUMA=n build errorStephen reports that an x86 allmodconfig build fails to build theof_pmem driver due to a missing definition of of_node_to_nid(). Thathelper is currently only exported in the OF_NUMA=y case. In other cases,ppc and sparc, it is a weak symbol, and outside of those platforms it isa static inline.Until an OF_NUMA=n configuration can reliably support usage ofof_node_to_nid() in modules across architectures, mark this driver as&apos;bool&apos; instead of &apos;tristate&apos;.Cc: Rob Herring &lt;robh@kernel.org&gt;Cc: Oliver O&apos;Halloran &lt;oohall@gmail.com&gt;Reported-by: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Mon, 09 Apr 2018 16:10:22 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>71719760 - libnvdimm: Add device-tree based driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#71719760</link>
        <description>libnvdimm: Add device-tree based driverThis patch adds peliminary device-tree bindings for persistent memoryregions. The driver registers a libnvdimm bus for each pmem-regionnode and each address range under the node is converted to a regionwithin that bus.Signed-off-by: Oliver O&apos;Halloran &lt;oohall@gmail.com&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Fri, 06 Apr 2018 05:21:14 +0000</pubDate>
        <dc:creator>Oliver O&apos;Halloran &lt;oohall@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>2080e88a - dax: introduce CONFIG_DAX_DRIVER</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#2080e88a</link>
        <description>dax: introduce CONFIG_DAX_DRIVERIn support of allowing device-mapper to compile out idle/dead code whenthere are no dax providers in the system, introduce the DAX_DRIVERsymbol. This is selected by all leaf drivers that device-mapper might belayered on top. This allows device-mapper to conditionally &apos;select DAX&apos;only when a provider is present.Cc: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;Cc: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;Reported-by: Bart Van Assche &lt;Bart.VanAssche@wdc.com&gt;Reviewed-by: Mike Snitzer &lt;snitzer@redhat.com&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Fri, 30 Mar 2018 00:20:39 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>83fc61a5 - treewide: Fix typos in Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#83fc61a5</link>
        <description>treewide: Fix typos in KconfigThis patch fixes some spelling typos found in Kconfig files.Signed-off-by: Masanari Iida &lt;standby24x7@gmail.com&gt;Acked-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Tue, 26 Sep 2017 03:47:59 +0000</pubDate>
        <dc:creator>Masanari Iida &lt;standby24x7@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>c1d6e828 - pmem: add dax_operations support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#c1d6e828</link>
        <description>pmem: add dax_operations supportSetup a dax_device to have the same lifetime as the pmem block deviceand add a -&gt;direct_access() method that is equivalent topmem_direct_access(). Once fs/dax.c has been converted to usedax_operations the old pmem_direct_access() will be removed.Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Wed, 25 Jan 2017 07:02:09 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>867dfe34 - nvdimm: make CONFIG_NVDIMM_DAX &apos;bool&apos;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#867dfe34</link>
        <description>nvdimm: make CONFIG_NVDIMM_DAX &apos;bool&apos;A bugfix just tried to address a randconfig build problem and introduceda variant of the same problem: with CONFIG_LIBNVDIMM=y andCONFIG_NVDIMM_DAX=m, the nvdimm module now fails to link:drivers/nvdimm/built-in.o: In function `to_nd_device_type&apos;:bus.c:(.text+0x1b5d): undefined reference to `is_nd_dax&apos;drivers/nvdimm/built-in.o: In function `nd_region_notify_driver_action.constprop.2&apos;:region_devs.c:(.text+0x6b6c): undefined reference to `is_nd_dax&apos;region_devs.c:(.text+0x6b8c): undefined reference to `to_nd_dax&apos;drivers/nvdimm/built-in.o: In function `nd_region_probe&apos;:region.c:(.text+0x70f3): undefined reference to `nd_dax_create&apos;drivers/nvdimm/built-in.o: In function `mode_show&apos;:namespace_devs.c:(.text+0xa196): undefined reference to `is_nd_dax&apos;drivers/nvdimm/built-in.o: In function `nvdimm_namespace_common_probe&apos;:(.text+0xa55f): undefined reference to `is_nd_dax&apos;drivers/nvdimm/built-in.o: In function `nvdimm_namespace_common_probe&apos;:(.text+0xa56e): undefined reference to `to_nd_dax&apos;This reverts the earlier fix, making NVDIMM_DAX a &apos;bool&apos; option againas it should be (it gets linked into the libnvdimm module). To fixthe original problem, I&apos;m adding a dependency on LIBNVDIMM toDEV_DAX_PMEM, which ensures we can&apos;t have that one built-in if therest is a module.Fixes: 4e65e9381c7a (&quot;/dev/dax: fix Kconfig dependency build breakage&quot;)Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Reviewed-by: Ross Zwisler &lt;ross.zwisler@linux.intel.com&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Tue, 25 Oct 2016 15:52:04 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>8c27ceff - docs: fix locations of several documents that got moved</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#8c27ceff</link>
        <description>docs: fix locations of several documents that got movedThe previous patch renamed several files that are cross-referencedalong the Kernel documentation. Adjust the links to point tothe right places.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Tue, 18 Oct 2016 12:12:27 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab@s-opensource.com&gt;</dc:creator>
    </item>
<item>
        <title>4e65e938 - /dev/dax: fix Kconfig dependency build breakage</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/nvdimm/Kconfig#4e65e938</link>
        <description>/dev/dax: fix Kconfig dependency build breakageThe function dax_pmem_probe() in drivers/dax/pmem.c is compiled under theCONFIG_DEV_DAX_PMEM tri-state config option.  This config option currentlyonly depends on CONFIG_NVDIMM_DAX, a bool, which means that the followingconfiguration is possible:CONFIG_LIBNVDIMM=m...CONFIG_NVDIMM_DAX=yCONFIG_DEV_DAX=yCONFIG_DEV_DAX_PMEM=yWith this config LIBNVDIMM is compiled as a module with NVDIMM_DAX=y justmeaning that we will compile drivers/nvdimm/dax_devs.c into that module.However, dax_pmem_probe() depends on several symbols defined indrivers/nvdimm/dax_devs.c, which results in the following build errors:drivers/built-in.o: In function `dax_pmem_probe&apos;:linux/drivers/dax/pmem.c:70: undefined reference to `to_nd_dax&apos;linux/drivers/dax/pmem.c:74: undefined reference to`nvdimm_namespace_common_probe&apos;linux/drivers/dax/pmem.c:80: undefined reference to `devm_nsio_enable&apos;linux/drivers/dax/pmem.c:81: undefined reference to `nvdimm_setup_pfn&apos;linux/drivers/dax/pmem.c:84: undefined reference to `devm_nsio_disable&apos;linux/drivers/dax/pmem.c:122: undefined reference to `to_nd_region&apos;drivers/built-in.o: In function `dax_pmem_init&apos;:linux/drivers/dax/pmem.c:147: undefined reference to `__nd_driver_register&apos;Fix this by making NVDIMM_DAX a tristate.  DEV_DAX_PMEM depends onNVDIMM_DAX which depends on LIBNVDIMM.  Since they are all now tristates,if LIBNVDIMM is built as a kernel module DEV_DAX_PMEM will be as well.This prevents dax_devs.c from being built as a built-in while itsdependencies are in the libnvdimm.ko module.Signed-off-by: Ross Zwisler &lt;ross.zwisler@linux.intel.com&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/nvdimm/Kconfig</description>
        <pubDate>Mon, 12 Sep 2016 16:15:07 +0000</pubDate>
        <dc:creator>Ross Zwisler &lt;ross.zwisler@linux.intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
