<?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>2e4986cf - fwctl: Add basic structure for a class subsystem with a cdev</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#2e4986cf</link>
        <description>fwctl: Add basic structure for a class subsystem with a cdevCreate the class, character device and functions for a fwctl driver toun/register to the subsystem.A typical fwctl driver has a sysfs presence like:$ ls -l /dev/fwctl/fwctl0crw------- 1 root root 250, 0 Apr 25 19:16 /dev/fwctl/fwctl0$ ls /sys/class/fwctl/fwctl0dev  device  power  subsystem  uevent$ ls /sys/class/fwctl/fwctl0/device/infiniband/ibp0s10f0$ ls /sys/class/infiniband/ibp0s10f0/device/fwctl/fwctl0/$ ls /sys/devices/pci0000:00/0000:00:0a.0/fwctl/fwctl0dev  device  power  subsystem  ueventWhich allows userspace to link all the multi-subsystem driver componentstogether and learn the subsystem specific names for the device&apos;scomponents.Link: https://patch.msgid.link/r/1-v5-642aa0c94070+4447f-fwctl_jgg@nvidia.comReviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Reviewed-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Reviewed-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Reviewed-by: Shannon Nelson &lt;shannon.nelson@amd.com&gt;Tested-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Tested-by: Shannon Nelson &lt;shannon.nelson@amd.com&gt;Signed-off-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Fri, 28 Feb 2025 00:26:29 +0000</pubDate>
        <dc:creator>Jason Gunthorpe &lt;jgg@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>9a6c7821 - vlynq: remove bus driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#9a6c7821</link>
        <description>vlynq: remove bus driverThere are no users with a vlynq_driver in the Kernel tree. Also, onlythe AR7 platform ever initialized a VLYNQ bus, but AR7 is going to beremoved from the Kernel. OpenWRT had some out-of-tree drivers which theyprobably intended to upport, but AR7 devices are even there notsupported anymore because they are &quot;stuck with Kernel3.18&quot; [1]. This code can go.[1] https://openwrt.org/docs/techref/targets/ar7Signed-off-by: Wolfram Sang &lt;wsa+renesas@sang-engineering.com&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Acked-by: Florian Fainelli &lt;f.fainelli@gmail.com&gt;Signed-off-by: Thomas Bogendoerfer &lt;tsbogend@alpha.franken.de&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Fri, 22 Sep 2023 06:15:24 +0000</pubDate>
        <dc:creator>Wolfram Sang &lt;wsa+renesas@sang-engineering.com&gt;</dc:creator>
    </item>
<item>
        <title>d149718e - pmdomain: Prepare to move Kconfig files into the pmdomain subsystem</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#d149718e</link>
        <description>pmdomain: Prepare to move Kconfig files into the pmdomain subsystemRather than having the various Kconfig files for the genpd providerssprinkled across subsystems, let&apos;s prepare to move them into the pmdomainsubsystem along with the implementations.Reviewed-by: Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;Signed-off-by: Ulf Hansson &lt;ulf.hansson@linaro.org&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Mon, 11 Sep 2023 15:22:15 +0000</pubDate>
        <dc:creator>Ulf Hansson &lt;ulf.hansson@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>9431063a - dpll: core: Add DPLL framework base functions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#9431063a</link>
        <description>dpll: core: Add DPLL framework base functionsDPLL framework is used to represent and configure DPLL devicesin systems. Each device that has DPLL and can configure inputsand outputs can use this framework.Implement core framework functions for further interactionswith device drivers implementing dpll subsystem, as well as forinteractions of DPLL netlink framework part with the subsystemitself.Co-developed-by: Milena Olech &lt;milena.olech@intel.com&gt;Signed-off-by: Milena Olech &lt;milena.olech@intel.com&gt;Co-developed-by: Michal Michalik &lt;michal.michalik@intel.com&gt;Signed-off-by: Michal Michalik &lt;michal.michalik@intel.com&gt;Signed-off-by: Vadim Fedorenko &lt;vadim.fedorenko@linux.dev&gt;Co-developed-by: Arkadiusz Kubalewski &lt;arkadiusz.kubalewski@intel.com&gt;Signed-off-by: Arkadiusz Kubalewski &lt;arkadiusz.kubalewski@intel.com&gt;Signed-off-by: Jiri Pirko &lt;jiri@nvidia.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Wed, 13 Sep 2023 20:49:37 +0000</pubDate>
        <dc:creator>Vadim Fedorenko &lt;vadim.fedorenko@linux.dev&gt;</dc:creator>
    </item>
<item>
        <title>d34599bc - cache: Add L2 cache management for Andes AX45MP RISC-V core</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#d34599bc</link>
        <description>cache: Add L2 cache management for Andes AX45MP RISC-V coreI/O Coherence Port (IOCP) provides an AXI interface for connectingexternal non-caching masters, such as DMA controllers. The accessesfrom IOCP are coherent with D-Caches and L2 Cache.IOCP is a specification option and is disabled on the Renesas RZ/FiveSoC due to this reason IP blocks using DMA will fail.The Andes AX45MP core has a Programmable Physical Memory Attributes (PMA)block that allows dynamic adjustment of memory attributes in the runtime.It contains a configurable amount of PMA entries implemented as CSRregisters to control the attributes of memory locations in interest.Below are the memory attributes supported:* Device, Non-bufferable* Device, bufferable* Memory, Non-cacheable, Non-bufferable* Memory, Non-cacheable, Bufferable* Memory, Write-back, No-allocate* Memory, Write-back, Read-allocate* Memory, Write-back, Write-allocate* Memory, Write-back, Read and Write-allocateMore info about PMA (section 10.3):Link: http://www.andestech.com/wp-content/uploads/AX45MP-1C-Rev.-5.0.0-Datasheet.pdfAs a workaround for SoCs with IOCP disabled CMO needs to be handled bysoftware. Firstly OpenSBI configures the memory region as&quot;Memory, Non-cacheable, Bufferable&quot; and passes this region as a globalshared dma pool as a DT node. With DMA_GLOBAL_POOL enabled all DMAallocations happen from this region and synchronization callbacks areimplemented to synchronize when doing DMA transactions.Example PMA region passes as a DT node from OpenSBI:    reserved-memory {        #address-cells = &lt;2&gt;;        #size-cells = &lt;2&gt;;        ranges;        pma_resv0@58000000 {            compatible = &quot;shared-dma-pool&quot;;            reg = &lt;0x0 0x58000000 0x0 0x08000000&gt;;            no-map;            linux,dma-default;        };    };Signed-off-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;Reviewed-by: Conor Dooley &lt;conor.dooley@microchip.com&gt;Tested-by: Conor Dooley &lt;conor.dooley@microchip.com&gt; # tyre-kicking on a d1Link: https://lore.kernel.org/r/20230818135723.80612-6-prabhakar.mahadev-lad.rj@bp.renesas.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Fri, 18 Aug 2023 13:57:22 +0000</pubDate>
        <dc:creator>Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;</dc:creator>
    </item>
<item>
        <title>c0191dd6 - video: Add auxiliary display drivers to Graphics support menu</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#c0191dd6</link>
        <description>video: Add auxiliary display drivers to Graphics support menuThe drivers in this subsystem are for either character-based or monochromeLCD controllers. Which can fall into the same category of the DRM/KMS andfbdev drivers, that are located under the &quot;Graphics support&quot; menu.Add the auxdisplay drivers there as well to have all display drivers underthe same menu.Suggested-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Signed-off-by: Javier Martinez Canillas &lt;javierm@redhat.com&gt;Reviewed-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Tested-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Helge Deller &lt;deller@gmx.de&gt;Acked-by: Miguel Ojeda &lt;ojeda@kernel.org&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20230719081544.741051-2-javierm@redhat.com

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Wed, 19 Jul 2023 08:15:35 +0000</pubDate>
        <dc:creator>Javier Martinez Canillas &lt;javierm@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>2959ab24 - cdx: add the cdx bus driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#2959ab24</link>
        <description>cdx: add the cdx bus driverIntroduce AMD CDX bus, which provides a mechanism for scanningand probing CDX devices. These devices are memory mapped onsystem bus for Application Processors(APUs).CDX devices can be changed dynamically in the Fabric and CDXbus interacts with CDX controller to rescan the bus andrediscover the devices.Signed-off-by: Nipun Gupta &lt;nipun.gupta@amd.com&gt;Reviewed-by: Pieter Jansen van Vuuren &lt;pieter.jansen-van-vuuren@amd.com&gt;Tested-by: Nikhil Agarwal &lt;nikhil.agarwal@amd.com&gt;Link: https://lore.kernel.org/r/20230313132636.31850-2-nipun.gupta@amd.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Mon, 13 Mar 2023 13:26:30 +0000</pubDate>
        <dc:creator>Nipun Gupta &lt;nipun.gupta@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>8bf48897 - drivers/accel: define kconfig and register a new major</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#8bf48897</link>
        <description>drivers/accel: define kconfig and register a new majorAdd a new Kconfig for the accel subsystem. The Kconfig currentlycontains only the basic CONFIG_DRM_ACCEL option that will be used todecide whether to compile the accel registration code. Therefore, thekconfig option is defined as bool.The accel code will be compiled as part of drm.ko and will be calleddirectly from the DRM core code. The reason we compile it as part ofdrm.ko and not as a separate module is because of cyclic dependencybetween drm.ko and the separate module (if it would have existed).This is due to the fact that DRM core code calls accel functions andvice-versa.The accelerator devices will be exposed to the user space with a new,dedicated major number - 261.The accel init function registers the new major number as a char deviceand create corresponding sysfs and debugfs root entries, similar towhat is done in DRM init function.I added a new header called drm_accel.h to include/drm/, that will holdthe prototypes of the drm_accel.c functions. In case CONFIG_DRM_ACCELis set to &apos;N&apos;, that header will contain empty inline implementations ofthose functions, to allow DRM core code to compile successfullywithout dependency on CONFIG_DRM_ACCEL.I Updated the MAINTAINERS file accordingly with the newly added folderand I have taken the liberty to appropriate the dri-devel mailing listand the dri-devel IRC channel for the accel subsystem.Signed-off-by: Oded Gabbay &lt;ogabbay@kernel.org&gt;Reviewed-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Reviewed-by: Jeffrey Hugo &lt;quic_jhugo@quicinc.com&gt;Reviewed-by: Dave Airlie &lt;airlied@redhat.com&gt;Acked-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Acked-by: Jacek Lawrynowicz &lt;jacek.lawrynowicz@linux.intel.com&gt;Tested-by: Jacek Lawrynowicz &lt;jacek.lawrynowicz@linux.intel.com&gt;Reviewed-by: Melissa Wen &lt;mwen@igalia.com&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Mon, 31 Oct 2022 13:28:35 +0000</pubDate>
        <dc:creator>Oded Gabbay &lt;ogabbay@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>35ba63b8 - vme: move back to staging</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#35ba63b8</link>
        <description>vme: move back to stagingThe VME subsystem graduated from staging into a top-level subsystem in2012, with commit db3b9e990e75 (&quot;Staging: VME: move VME drivers out ofstaging&quot;) stating:    The VME device drivers have not moved out yet due to some API    questions they are still working through, that should happen soon,    hopefully.However, this never happened: maintenance of drivers/vme effectivelystopped in 2017, with all subsequent changes being treewide cleanups.No hardware driver remains in staging, only the limited user-levelaccess, and I just removed one of the two bridge drivers and the onlyremaining board.drivers/staging/vme/devices/ was recently moved todrivers/staging/vme_user/, but as the vme_user driver is the only oneremaining for this subsystem, it is easier to just move the remainingthree source files into this directory rather than keeping the originalhierarchy.Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://lore.kernel.org/r/20220606084109.4108188-3-arnd@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Mon, 06 Jun 2022 08:41:05 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>dd11376b - scsi: ufs: Split the drivers/scsi/ufs directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#dd11376b</link>
        <description>scsi: ufs: Split the drivers/scsi/ufs directorySplit the drivers/scsi/ufs directory into &apos;core&apos; and &apos;host&apos; directoriesunder the drivers/ufs/ directory. Move shared header files into theinclude/ufs/ directory. This separation makes it clear which header filesUFS drivers are allowed to include (include/ufs/*.h) and which header filesUFS drivers are not allowed to include (drivers/ufs/core/*.h).Update the MAINTAINERS file. Add myself as a UFS reviewer.Link: https://lore.kernel.org/r/20220511212552.655341-1-bvanassche@acm.orgCc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Avri Altman &lt;avri.altman@wdc.com&gt;Cc: Bean Huo &lt;beanhuo@micron.com&gt;Cc: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Cc: Keoseong Park &lt;keosung.park@samsung.com&gt;Tested-by: Bean Huo &lt;beanhuo@micron.com&gt;Tested-by: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Reviewed-by: Bean Huo &lt;beanhuo@micron.com&gt;Acked-by: Avri Altman &lt;avri.altman@wdc.com&gt;Acked-by: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Signed-off-by: Bart Van Assche &lt;bvanassche@acm.org&gt;Signed-off-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Wed, 11 May 2022 21:25:52 +0000</pubDate>
        <dc:creator>Bart Van Assche &lt;bvanassche@acm.org&gt;</dc:creator>
    </item>
<item>
        <title>31ab09b4 - drivers: Add hardware timestamp engine (HTE) subsystem</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#31ab09b4</link>
        <description>drivers: Add hardware timestamp engine (HTE) subsystemSome devices can timestamp system lines/signals/Buses in real-timeusing the hardware counter or other hardware means which can givefiner granularity and help avoid jitter introduced by softwaretimestamping. To utilize such functionality, this patchset createsHTE subsystem where devices can register themselves as providers sothat the consumers devices can request specific line from theproviders. The patch also adds compilation support in Makefile andmenu options in Kconfig.The provider does following:- Registers chip with the framework.- Provides translation hook to convert logical line id.- Provides enable/disable, request/release callbacks.- Pushes timestamp data to HTE subsystem.The consumer does following:- Initializes line attribute.- Gets HTE timestamp descriptor.- Requests timestamp functionality.- Puts HTE timestamp descriptor.Signed-off-by: Dipen Patel &lt;dipenp@nvidia.com&gt;Reported-by: kernel test robot &lt;lkp@intel.com&gt;Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Fri, 22 Apr 2022 20:52:13 +0000</pubDate>
        <dc:creator>Dipen Patel &lt;dipenp@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>e5f45b01 - staging: Remove the drivers for the Unisys s-Par</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#e5f45b01</link>
        <description>staging: Remove the drivers for the Unisys s-ParThe Unisys sub-tree of drivers/staging contains three drivers for the&quot;Unisys Secure Partition&quot; (s-Par(R)): visorhba, visorinput, visornic.They have no maintainers, in fact the only one that is listed inMAINTAINERS has an unreacheable email address. During 2021 and 2022several patches have been submitted to these drivers but nobody atUnisys cared of reviewing the changes. Probably, also the&quot;sparmaintainer&quot; internal list of unisys.com is not anymore read byinterested Unisys&apos; engineers.Therefore, remove the drivers/staging/unisys directory and delete therelevant entries in the MAINTAINERS, Kconfig, Makefile files, thenremove also the drivers/visorbus directory which is not anymore needed(it contained the driver for the virtualized bus for the Unisys s-Parfirmware).Cc: David Kershner &lt;david.kershner@unisys.com&gt;Cc: &lt;sparmaintainer@unisys.com&gt;Cc: Ken Cox &lt;jkc@redhat.com&gt;Suggested-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Fabio M. De Francesco &lt;fmdefrancesco@gmail.com&gt;Link: https://lore.kernel.org/r/20220414103217.32058-1-fmdefrancesco@gmail.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Thu, 14 Apr 2022 10:32:17 +0000</pubDate>
        <dc:creator>Fabio M. De Francesco &lt;fmdefrancesco@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>6523d3b2 - peci: Add core infrastructure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#6523d3b2</link>
        <description>peci: Add core infrastructureIntel processors provide access for various services designed to supportprocessor and DRAM thermal management, platform manageability andprocessor interface tuning and diagnostics.Those services are available via the Platform Environment ControlInterface (PECI) that provides a communication channel between theprocessor and the Baseboard Management Controller (BMC) or otherplatform management device.This change introduces PECI subsystem by adding the initial core moduleand API for controller drivers.Co-developed-by: Jason M Bills &lt;jason.m.bills@linux.intel.com&gt;Co-developed-by: Jae Hyun Yoo &lt;jae.hyun.yoo@linux.intel.com&gt;Reviewed-by: Pierre-Louis Bossart &lt;pierre-louis.bossart@linux.intel.com&gt;Acked-by: Joel Stanley &lt;joel@jms.id.au&gt;Signed-off-by: Jason M Bills &lt;jason.m.bills@linux.intel.com&gt;Signed-off-by: Jae Hyun Yoo &lt;jae.hyun.yoo@linux.intel.com&gt;Signed-off-by: Iwona Winiarska &lt;iwona.winiarska@intel.com&gt;Link: https://lore.kernel.org/r/20220208153639.255278-5-iwona.winiarska@intel.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Tue, 08 Feb 2022 15:36:30 +0000</pubDate>
        <dc:creator>Iwona Winiarska &lt;iwona.winiarska@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>951cd3a0 - firmware: include drivers/firmware/Kconfig unconditionally</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#951cd3a0</link>
        <description>firmware: include drivers/firmware/Kconfig unconditionallyCompile-testing drivers that require access to a firmware layerfails when that firmware symbol is unavailable. This happenedtwice this week: - My proposed to change to rework the QCOM_SCM firmware symbol   broke on ppc64 and others. - The cs_dsp firmware patch added device specific firmware loader   into drivers/firmware, which broke on the same set of   architectures.We should probably do the same thing for other subsystems as well,but fix this one first as this is a dependency for other patchesgetting merged.Reviewed-by: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Reviewed-by: Charles Keepax &lt;ckeepax@opensource.cirrus.com&gt;Acked-by: Will Deacon &lt;will@kernel.org&gt;Acked-by: Bjorn Andersson &lt;bjorn.andersson@linaro.org&gt;Cc: Mark Brown &lt;broonie@kernel.org&gt;Cc: Liam Girdwood &lt;lgirdwood@gmail.com&gt;Cc: Charles Keepax &lt;ckeepax@opensource.cirrus.com&gt;Cc: Simon Trimmer &lt;simont@opensource.cirrus.com&gt;Cc: Michael Ellerman &lt;mpe@ellerman.id.au&gt;Reviewed-by: Mark Brown &lt;broonie@kernel.org&gt;Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Tue, 28 Sep 2021 07:50:26 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>9ea9b9c4 - remove the lightnvm subsystem</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#9ea9b9c4</link>
        <description>remove the lightnvm subsystemLightnvm supports the OCSSD 1.x and 2.0 specs which were early attemptsto produce Open Channel SSDs and never made it into the NVMe specproper.  They have since been superceeded by NVMe enhancements suchas ZNS support.  Remove the support per the deprecation schedule.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Link: https://lore.kernel.org/r/20210812132308.38486-1-hch@lst.deReviewed-by: Matias Bj&#248;rling &lt;mb@lightnvm.io&gt;Reviewed-by: Javier Gonz&#225;lez &lt;javier@javigon.com&gt;Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Thu, 12 Aug 2021 13:23:08 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>b7fb14d3 - ide: remove the legacy ide driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#b7fb14d3</link>
        <description>ide: remove the legacy ide driverThe legay ide driver has been replace with libata starting in 2003 and hasbeen scheduled for removal for a while.  Finally kill it off so that wecan start cleaning up various bits of cruft it forced on the block layer.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Wed, 16 Jun 2021 13:46:58 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>8ffdff6a - staging: comedi: move out of staging directory</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#8ffdff6a</link>
        <description>staging: comedi: move out of staging directoryThe comedi code came into the kernel back in 2008, but traces itslifetime to much much earlier.  It&apos;s been polished and buffed andthere&apos;s really nothing preventing it from being part of the &quot;real&quot;portion of the kernel.So move it to drivers/comedi/ as it belongs there.Many thanks to the hundreds of developers who did the work to make thishappen.Cc: Ian Abbott &lt;abbotti@mev.co.uk&gt;Cc: H Hartley Sweeten &lt;hsweeten@visionengravers.com&gt;Link: https://lore.kernel.org/r/YHauop4u3sP6lz8j@kroah.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Wed, 14 Apr 2021 08:58:10 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>4cdadfd5 - cxl/mem: Introduce a driver for CXL-2.0-Type-3 endpoints</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#4cdadfd5</link>
        <description>cxl/mem: Introduce a driver for CXL-2.0-Type-3 endpointsThe CXL.mem protocol allows a device to act as a provider of &quot;SystemRAM&quot; and/or &quot;Persistent Memory&quot; that is fully coherent as if the memorywas attached to the typical CPU memory controller.With the CXL-2.0 specification a PCI endpoint can implement a &quot;Type-3&quot;device interface and give the operating system control over &quot;HostManaged Device Memory&quot;. See section 2.3 Type 3 CXL Device.The memory range exported by the device may optionally be described bythe platform firmware memory map, or by infrastructure like LIBNVDIMM toprovision persistent memory capacity from one, or more, CXL.mem devices.A pre-requisite for Linux-managed memory-capacity provisioning is thiscxl_mem driver that can speak the mailbox protocol defined in section8.2.8.4 Mailbox Registers.For now just land the initial driver boiler-plate and Documentation/infrastructure.Signed-off-by: Ben Widawsky &lt;ben.widawsky@intel.com&gt;Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Acked-by: David Rientjes &lt;rientjes@google.com&gt; (v1)Cc: Jonathan Corbet &lt;corbet@lwn.net&gt;Link: https://www.computeexpresslink.org/download-the-specificationLink: https://lore.kernel.org/r/20210217040958.1354670-2-ben.widawsky@intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Wed, 17 Feb 2021 04:09:50 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>c9b9f5f8 - vdpa: move to drivers/vdpa</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#c9b9f5f8</link>
        <description>vdpa: move to drivers/vdpaWe have both vhost and virtio drivers that depend on vdpa.It&apos;s easier to locate it at a top level directory otherwisewe run into issues e.g. if vhost is built-in but virtiois modular.  Let&apos;s just move it up a level.Reported-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Tue, 31 Mar 2020 19:15:14 +0000</pubDate>
        <dc:creator>Michael S. Tsirkin &lt;mst@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>20c384f1 - vhost: refine vhost and vringh kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/Kconfig#20c384f1</link>
        <description>vhost: refine vhost and vringh kconfigCurrently, CONFIG_VHOST depends on CONFIG_VIRTUALIZATION. But vhost isnot necessarily for VM since it&apos;s a generic userspace and kernelcommunication protocol. Such dependency may prevent archs withoutvirtualization support from using vhost.To solve this, a dedicated vhost menu is created under drivers soCONIFG_VHOST can be decoupled out of CONFIG_VIRTUALIZATION.While at it, also squash Kconfig.vringh into vhost Kconfig file. Thisavoids the trick of conditional inclusion from VOP or CAIF. Then itwill be easier to introduce new vringh users and common dependency forboth vringh and vhost.Signed-off-by: Jason Wang &lt;jasowang@redhat.com&gt;Link: https://lore.kernel.org/r/20200326140125.19794-2-jasowang@redhat.comSigned-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/Kconfig</description>
        <pubDate>Thu, 26 Mar 2020 14:01:17 +0000</pubDate>
        <dc:creator>Jason Wang &lt;jasowang@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
