<?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>76750765 - arch_numa: switch over to numa_memblks</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#76750765</link>
        <description>arch_numa: switch over to numa_memblksUntil now arch_numa was directly translating firmware NUMA informationto memblock.Using numa_memblks as an intermediate step has a few advantages:* alignment with more battle tested x86 implementation* availability of NUMA emulation* maintaining node information for not yet populated memoryAdjust a few places in numa_memblks to compile with 32-bit phys_addr_t andreplace current functionality related to numa_add_memblk() and__node_distance() in arch_numa with the implementation based onnuma_memblks and add functions required by numa_emulation.[rppt@kernel.org: fix section mismatch]  Link: https://lkml.kernel.org/r/ZrO6cExVz1He_yPn@kernel.org[rppt@kernel.org: PFN_PHYS() translation is unnecessary here]  Link: https://lkml.kernel.org/r/Zs2T5wkSYO9MGcab@kernel.orgLink: https://lkml.kernel.org/r/20240807064110.1003856-25-rppt@kernel.orgSigned-off-by: Mike Rapoport (Microsoft) &lt;rppt@kernel.org&gt;Tested-by: Zi Yan &lt;ziy@nvidia.com&gt; # for x86_64 and arm64Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Tested-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt; [arm64 + CXL via QEMU]Acked-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Acked-by: David Hildenbrand &lt;david@redhat.com&gt;Cc: Alexander Gordeev &lt;agordeev@linux.ibm.com&gt;Cc: Andreas Larsson &lt;andreas@gaisler.com&gt;Cc: Arnd Bergmann &lt;arnd@arndb.de&gt;Cc: Borislav Petkov &lt;bp@alien8.de&gt;Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Cc: Christophe Leroy &lt;christophe.leroy@csgroup.eu&gt;Cc: Dave Hansen &lt;dave.hansen@linux.intel.com&gt;Cc: Davidlohr Bueso &lt;dave@stgolabs.net&gt;Cc: David S. Miller &lt;davem@davemloft.net&gt;Cc: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Cc: Heiko Carstens &lt;hca@linux.ibm.com&gt;Cc: Huacai Chen &lt;chenhuacai@kernel.org&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: Jiaxun Yang &lt;jiaxun.yang@flygoat.com&gt;Cc: John Paul Adrian Glaubitz &lt;glaubitz@physik.fu-berlin.de&gt;Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Cc: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Cc: Palmer Dabbelt &lt;palmer@dabbelt.com&gt;Cc: Rafael J. Wysocki &lt;rafael@kernel.org&gt;Cc: Rob Herring (Arm) &lt;robh@kernel.org&gt;Cc: Samuel Holland &lt;samuel.holland@sifive.com&gt;Cc: Thomas Bogendoerfer &lt;tsbogend@alpha.franken.de&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Cc: Vasily Gorbik &lt;gor@linux.ibm.com&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Wed, 07 Aug 2024 06:41:08 +0000</pubDate>
        <dc:creator>Mike Rapoport (Microsoft) &lt;rppt@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>8ad266d1 - driver core: Add CONFIG_FW_DEVLINK_SYNC_STATE_TIMEOUT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#8ad266d1</link>
        <description>driver core: Add CONFIG_FW_DEVLINK_SYNC_STATE_TIMEOUTAdd a build time equivalent of fw_devlink.sync_state=timeout so thatboard specific kernels could enable it and not have to deal with settingor cluttering the kernel commandline.Cc: Doug Anderson &lt;dianders@chromium.org&gt;Signed-off-by: Saravana Kannan &lt;saravanak@google.com&gt;Reviewed-by: Douglas Anderson &lt;dianders@chromium.org&gt;Link: https://lore.kernel.org/r/20230317205134.964098-1-saravanak@google.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Fri, 17 Mar 2023 20:51:33 +0000</pubDate>
        <dc:creator>Saravana Kannan &lt;saravanak@google.com&gt;</dc:creator>
    </item>
<item>
        <title>28f0c335 - devtmpfs: mount with noexec and nosuid</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#28f0c335</link>
        <description>devtmpfs: mount with noexec and nosuiddevtmpfs is writable. Add the noexec and nosuid as default mount flagsto prevent code execution from /dev. The systems who don&apos;t use systemdand who rely on CONFIG_DEVTMPFS_MOUNT=y are the ones to be protected bythis patch. Other systems are fine with the udev solution.No sane program should be relying on executing from /dev. So this patchreduces the attack surface. It doesn&apos;t prevent any specific attack, butit reduces the possibility that someone can use /dev as a place to putexecutable code. Chrome OS has been carrying this patch for severalyears. It seems trivial and simple solution to improve the protection of/dev when CONFIG_DEVTMPFS_MOUNT=y.Original patch:https://lore.kernel.org/lkml/20121120215059.GA1859@www.outflux.net/Cc: ellyjones@chromium.orgCc: Kay Sievers &lt;kay@vrfy.org&gt;Cc: Roland Eggner &lt;edvx1@systemanalysen.net&gt;Co-developed-by: Muhammad Usama Anjum &lt;usama.anjum@collabora.com&gt;Signed-off-by: Kees Cook &lt;keescook@chromium.org&gt;Signed-off-by: Muhammad Usama Anjum &lt;usama.anjum@collabora.com&gt;Link: https://lore.kernel.org/r/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Wed, 22 Dec 2021 12:50:20 +0000</pubDate>
        <dc:creator>Kees Cook &lt;keescook@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>ae3c107c - numa: Move numa implementation to common code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#ae3c107c</link>
        <description>numa: Move numa implementation to common codeARM64 numa implementation is generic enough that RISC-V can reuse thatimplementation with very minor cosmetic changes. This will help bothARM64 and RISC-V in terms of maintanace and feature improvementMove the numa implementation code to common directory so that both ISAscan reuse this. This doesn&apos;t introduce any function changes for ARM64.Signed-off-by: Atish Patra &lt;atish.patra@wdc.com&gt;Acked-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Tested-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Signed-off-by: Palmer Dabbelt &lt;palmerdabbelt@google.com&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Thu, 19 Nov 2020 00:38:26 +0000</pubDate>
        <dc:creator>Atish Patra &lt;atish.patra@wdc.com&gt;</dc:creator>
    </item>
<item>
        <title>fb88c9a3 - drivers: base: Kconfig: fix spelling mistake &quot;heterogenous&quot; -&gt; &quot;heterogeneous&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#fb88c9a3</link>
        <description>drivers: base: Kconfig: fix spelling mistake &quot;heterogenous&quot; -&gt; &quot;heterogeneous&quot;There is a spelling mistake in the Kconfig help text. Fix it.Signed-off-by: Colin Ian King &lt;colin.king@canonical.com&gt;Link: https://lore.kernel.org/r/20201215145440.204362-1-colin.king@canonical.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Tue, 15 Dec 2020 14:54:40 +0000</pubDate>
        <dc:creator>Colin Ian King &lt;colin.king@canonical.com&gt;</dc:creator>
    </item>
<item>
        <title>7de3697e - Add auxiliary bus support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#7de3697e</link>
        <description>Add auxiliary bus supportAdd support for the Auxiliary Bus, auxiliary_device and auxiliary_driver.It enables drivers to create an auxiliary_device and bind anauxiliary_driver to it.The bus supports probe/remove shutdown and suspend/resume callbacks.Each auxiliary_device has a unique string based id; driver binds toan auxiliary_device based on this id through the bus.Co-developed-by: Kiran Patil &lt;kiran.patil@intel.com&gt;Co-developed-by: Ranjani Sridharan &lt;ranjani.sridharan@linux.intel.com&gt;Co-developed-by: Fred Oh &lt;fred.oh@linux.intel.com&gt;Co-developed-by: Leon Romanovsky &lt;leonro@nvidia.com&gt;Signed-off-by: Kiran Patil &lt;kiran.patil@intel.com&gt;Signed-off-by: Ranjani Sridharan &lt;ranjani.sridharan@linux.intel.com&gt;Signed-off-by: Fred Oh &lt;fred.oh@linux.intel.com&gt;Signed-off-by: Leon Romanovsky &lt;leonro@nvidia.com&gt;Signed-off-by: Dave Ertman &lt;david.m.ertman@intel.com&gt;Reviewed-by: Pierre-Louis Bossart &lt;pierre-louis.bossart@linux.intel.com&gt;Reviewed-by: Shiraz Saleem &lt;shiraz.saleem@intel.com&gt;Reviewed-by: Parav Pandit &lt;parav@mellanox.com&gt;Reviewed-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Reviewed-by: Martin Habets &lt;mhabets@solarflare.com&gt;Link: https://lore.kernel.org/r/20201113161859.1775473-2-david.m.ertman@intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Link: https://lore.kernel.org/r/160695681289.505290.8978295443574440604.stgit@dwillia2-desk3.amr.corp.intel.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Thu, 03 Dec 2020 00:54:24 +0000</pubDate>
        <dc:creator>Dave Ertman &lt;david.m.ertman@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>bebe94b5 - drivers: base: default KUNIT_* fragments to KUNIT_ALL_TESTS</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#bebe94b5</link>
        <description>drivers: base: default KUNIT_* fragments to KUNIT_ALL_TESTSThis makes it easier to enable all KUnit fragments.Adding &apos;if !KUNIT_ALL_TESTS&apos; so individual tests can not be turned off.Therefore if KUNIT_ALL_TESTS is enabled that will hide the prompt inmenuconfig.Reviewed-by: David Gow &lt;davidgow@google.com&gt;Signed-off-by: Anders Roxell &lt;anders.roxell@linaro.org&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Mon, 11 May 2020 13:14:33 +0000</pubDate>
        <dc:creator>Anders Roxell &lt;anders.roxell@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>35c57fc3 - kunit: building kunit as a module breaks allmodconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#35c57fc3</link>
        <description>kunit: building kunit as a module breaks allmodconfigkunit tests that do not support module build should dependon KUNIT=y rather than just KUNIT in Kconfig, otherwisethey will trigger compilation errors for &quot;make allmodconfig&quot;builds.Fixes: 9fe124bf1b77 (&quot;kunit: allow kunit to be loaded as a module&quot;)Reported-by: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;Signed-off-by: Alan Maguire &lt;alan.maguire@oracle.com&gt;Signed-off-by: Shuah Khan &lt;skhan@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Fri, 10 Jan 2020 11:49:25 +0000</pubDate>
        <dc:creator>Alan Maguire &lt;alan.maguire@oracle.com&gt;</dc:creator>
    </item>
<item>
        <title>14e08757 - PM / QoS: Initial kunit test</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#14e08757</link>
        <description>PM / QoS: Initial kunit testThe pm_qos family of APIs are used in relatively difficult to reproducescenarios such as thermal throttling so they benefit from unit testing.Start by adding basic tests from the the freq_qos APIs. It includestests for issues that were brought up on mailing lists:https://patchwork.kernel.org/patch/11252425/#23017005https://patchwork.kernel.org/patch/11253421/Signed-off-by: Leonard Crestez &lt;leonard.crestez@nxp.com&gt;Reviewed-by: Matthias Kaehlcke &lt;mka@chromium.org&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Tue, 26 Nov 2019 15:17:10 +0000</pubDate>
        <dc:creator>Leonard Crestez &lt;leonard.crestez@nxp.com&gt;</dc:creator>
    </item>
<item>
        <title>c181831f - base: arch_topology: update Kconfig help description</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#c181831f</link>
        <description>base: arch_topology: update Kconfig help descriptionCommit 5d777b185f6d (&quot;arch_topology: Make cpu_capacity sysfs node as read-only&quot;)made cpu_capacity sysfs node read-only. Update the GENERIC_ARCH_TOPOLOGYKconfig help section to reflect the same.Cc: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Sudeep Holla &lt;sudeep.holla@arm.com&gt;Signed-off-by: Paul Walmsley &lt;paul.walmsley@sifive.com&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Thu, 27 Jun 2019 19:53:01 +0000</pubDate>
        <dc:creator>Sudeep Holla &lt;sudeep.holla@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>5dd50aae - Make anon_inodes unconditional</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#5dd50aae</link>
        <description>Make anon_inodes unconditionalMake the anon_inodes facility unconditional so that it can be used by coreVFS code and pidfd code.Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;[christian@brauner.io: adapt commit message to mention pidfds]Signed-off-by: Christian Brauner &lt;christian@brauner.io&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Mon, 05 Nov 2018 17:40:31 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>e1cf33aa - node: Add heterogenous memory access attributes</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#e1cf33aa</link>
        <description>node: Add heterogenous memory access attributesHeterogeneous memory systems provide memory nodes with different latencyand bandwidth performance attributes. Provide a new kernel interfacefor subsystems to register the attributes under the memory targetnode&apos;s initiator access class. If the system provides this information,applications may query these attributes when deciding which node torequest memory.The following example shows the new sysfs hierarchy for a node exportingperformance attributes:  # tree -P &quot;read*|write*&quot;/sys/devices/system/node/nodeY/accessZ/initiators/  /sys/devices/system/node/nodeY/accessZ/initiators/  |-- read_bandwidth  |-- read_latency  |-- write_bandwidth  `-- write_latencyThe bandwidth is exported as MB/s and latency is reported innanoseconds. The values are taken from the platform as reported by themanufacturer.Memory accesses from an initiator node that is not one of the memory&apos;saccess &quot;Z&quot; initiator nodes linked in the same directory may observedifferent performance than reported here. When a subsystem makes useof this interface, initiators of a different access number may not havethe same performance relative to initiators in other access numbers, oromitted from the any access class&apos; initiators.Descriptions for memory access initiator performance access attributesare added to sysfs stable documentation.Acked-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Tested-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Signed-off-by: Keith Busch &lt;keith.busch@intel.com&gt;Reviewed-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;Tested-by: Brice Goglin &lt;Brice.Goglin@inria.fr&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Mon, 11 Mar 2019 20:56:01 +0000</pubDate>
        <dc:creator>Keith Busch &lt;keith.busch@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>1be01d4a - driver: base: Disable CONFIG_UEVENT_HELPER by default</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#1be01d4a</link>
        <description>driver: base: Disable CONFIG_UEVENT_HELPER by defaultSince commit 7934779a69f1184f (&quot;Driver-Core: disable /sbin/hotplug bydefault&quot;), the help text for the /sbin/hotplug fork-bomb says&quot;This should not be used today [...] creates a high system load, or[...] out-of-memory situations during bootup&quot;.  The rationale for thiswas that no recent mainstream system used this anymore (in 2010!).A few years later, the complete uevent helper support was made optionalin commit 86d56134f1b67d0c (&quot;kobject: Make support for uevent_helperoptional.&quot;).  However, if was still left enabled by default, to supportancient userland.Time passed by, and nothing should use this anymore, so it can bedisabled by default.Signed-off-by: Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Thu, 14 Mar 2019 11:13:50 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;</dc:creator>
    </item>
<item>
        <title>dadd2299 - Make anon_inodes unconditional</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#dadd2299</link>
        <description>Make anon_inodes unconditionalMake the anon_inodes facility unconditional so that it can be used by coreVFS code.Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Mon, 05 Nov 2018 17:40:31 +0000</pubDate>
        <dc:creator>David Howells &lt;dhowells@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>ddb26d8e - dma-mapping: move CONFIG_DMA_CMA to kernel/dma/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#ddb26d8e</link>
        <description>dma-mapping: move CONFIG_DMA_CMA to kernel/dma/KconfigThis is where all the related code already lives.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Wed, 13 Feb 2019 18:19:08 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>06bfd3c8 - firmware_loader: move kconfig FW_LOADER entries to its own file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#06bfd3c8</link>
        <description>firmware_loader: move kconfig FW_LOADER entries to its own fileThis will make it easier to track and easier to understandwhat components and features are part of the FW_LOADER. Thereare some components related to firmware which have *nothing* todo with the FW_LOADER, souch as PREVENT_FIRMWARE_BUILD.Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Signed-off-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Thu, 10 May 2018 20:08:43 +0000</pubDate>
        <dc:creator>Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>367d0982 - firmware_loader: replace ---help--- with help</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#367d0982</link>
        <description>firmware_loader: replace ---help--- with helpAs per checkpatch using help is preferred over ---help---.Signed-off-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Thu, 10 May 2018 20:08:42 +0000</pubDate>
        <dc:creator>Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>02c39930 - firmware_loader: enhance Kconfig documentation over FW_LOADER</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#02c39930</link>
        <description>firmware_loader: enhance Kconfig documentation over FW_LOADERIf you try to read FW_LOADER today it speaks of old riddles andunless you have been following development closely you will losetrack of what is what. Even the documentation for PREVENT_FIRMWARE_BUILDis a bit fuzzy and how it fits into this big picture.Give the FW_LOADER kconfig documentation some love with more up todate developments and recommendations. While at it, wrap the FW_LOADERcode into its own menu to compartmentalize and make it clearer whichcomponents really are part of the FW_LOADER. This should also makeit easier to later move these kconfig entries into the firmware_loader/directory later.This also now recommends using firmwared [0] for folks left needing auevent handler in userspace for the sysfs firmware fallback mechanisgiven udev&apos;s uevent firmware mechanism was ripped out a while ago.[0] https://github.com/teg/firmwaredReviewed-by: Kees Cook &lt;keescook@chromium.org&gt;Signed-off-by: Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Thu, 10 May 2018 20:08:41 +0000</pubDate>
        <dc:creator>Luis R. Rodriguez &lt;mcgrof@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>7f55c733 - firmware: Drop FIRMWARE_IN_KERNEL Kconfig option</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#7f55c733</link>
        <description>firmware: Drop FIRMWARE_IN_KERNEL Kconfig optionIt doesn&apos;t actually do anything.  Merge its help text intoEXTRA_FIRMWARE.Fixes: 5620a0d1aacd (&quot;firmware: delete in-kernel firmware&quot;)Fixes: 0946b2fb38fd (&quot;firmware: cleanup FIRMWARE_IN_KERNEL message&quot;)Signed-off-by: Benjamin Gilbert &lt;benjamin.gilbert@coreos.com&gt;Signed-off-by: Robin H. Johnson &lt;robbat2@gentoo.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Wed, 24 Jan 2018 02:06:31 +0000</pubDate>
        <dc:creator>Benjamin Gilbert &lt;benjamin.gilbert@coreos.com&gt;</dc:creator>
    </item>
<item>
        <title>87590ce6 - sysfs/cpu: Add vulnerability folder</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/base/Kconfig#87590ce6</link>
        <description>sysfs/cpu: Add vulnerability folderAs the meltdown/spectre problem affects several CPU architectures, it makessense to have common way to express whether a system is affected by aparticular vulnerability or not. If affected the way to express themitigation should be common as well.Create /sys/devices/system/cpu/vulnerabilities folder and files formeltdown, spectre_v1 and spectre_v2.Allow architectures to override the show function.Signed-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Konrad Rzeszutek Wilk &lt;konrad.wilk@oracle.com&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Will Deacon &lt;will.deacon@arm.com&gt;Cc: Dave Hansen &lt;dave.hansen@intel.com&gt;Cc: Linus Torvalds &lt;torvalds@linuxfoundation.org&gt;Cc: Borislav Petkov &lt;bp@alien8.de&gt;Cc: David Woodhouse &lt;dwmw@amazon.co.uk&gt;Link: https://lkml.kernel.org/r/20180107214913.096657732@linutronix.de

            List of files:
            /linux-6.15/drivers/base/Kconfig</description>
        <pubDate>Sun, 07 Jan 2018 21:48:00 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
</channel>
</rss>
