<?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>feb541bf - lib/crc64-rocksoft: stop wrapping the crypto API</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#feb541bf</link>
        <description>lib/crc64-rocksoft: stop wrapping the crypto APIFollowing what was done for the CRC32 and CRC-T10DIF library functions,get rid of the pointless use of the crypto API and makecrc64_rocksoft_update() call into the library directly.  This is fasterand simpler.Remove crc64_rocksoft() (the version of the function that did not take a&apos;crc&apos; argument) since it is unused.Reviewed-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;Reviewed-by: &quot;Martin K. Petersen&quot; &lt;martin.petersen@oracle.com&gt;Acked-by: Keith Busch &lt;kbusch@kernel.org&gt;Link: https://lore.kernel.org/r/20250130035130.180676-2-ebiggers@kernel.orgSigned-off-by: Eric Biggers &lt;ebiggers@google.com&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Thu, 30 Jan 2025 03:51:20 +0000</pubDate>
        <dc:creator>Eric Biggers &lt;ebiggers@google.com&gt;</dc:creator>
    </item>
<item>
        <title>e9f5f44a - block: remove the blk_integrity_profile structure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#e9f5f44a</link>
        <description>block: remove the blk_integrity_profile structureBlock layer integrity configuration is a bit complex right now, as itindirects through operation vectors for a simple two-dimensionalconfiguration: a) the checksum type of none, ip checksum, crc, crc64 b) the presence or absence of a reference tagRemove the integrity profile, and instead add a separate csum_type flagwhich replaces the existing ip-checksum field and a new flag thatindicates the presence of the reference tag.This removes up to two layers of indirect calls, remove the need tooffload the no-op verification of non-PI metadata to a workqueue andgenerally simplifies the code. The downside is that block/t10-pi.c nowhas to be built into the kernel when CONFIG_BLK_DEV_INTEGRITY issupported.  Given that both nvme and SCSI require t10-pi.ko, it is loadedfor all usual configurations that enabled CONFIG_BLK_DEV_INTEGRITYalready, though.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Kanchan Joshi &lt;joshi.k@samsung.com&gt;Reviewed-by: Hannes Reinecke &lt;hare@suse.de&gt;Reviewed-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;Link: https://lore.kernel.org/r/20240613084839.1044015-6-hch@lst.deSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Thu, 13 Jun 2024 08:48:15 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>bf20ab53 - blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOW</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#bf20ab53</link>
        <description>blk-throttle: remove CONFIG_BLK_DEV_THROTTLING_LOWOne the one hand, it&apos;s marked EXPERIMENTAL since 2017, and looks likethere are no users since then, and no testers and no developers, it&apos;sjust not active at all.On the other hand, even if the config is disabled, there are still manyfields in throtl_grp and throtl_data and many functions that are onlyused for throtl low.At last, currently blk-throtl is initialized during disk initialization,and destroyed during disk removal, and it exposes many functions to becalled directly from block layer.Remove throtl low to make code much more cleaner and follow up work mucheasier.Signed-off-by: Yu Kuai &lt;yukuai3@huawei.com&gt;Acked-by: Tejun Heo &lt;tj@kernel.org&gt;Link: https://lore.kernel.org/r/20240509121107.3195568-2-yukuai1@huaweicloud.comSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Thu, 09 May 2024 12:11:06 +0000</pubDate>
        <dc:creator>Yu Kuai &lt;yukuai3@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>97abee50 - block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONED</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#97abee50</link>
        <description>block: Do not force select mq-deadline with CONFIG_BLK_DEV_ZONEDNow that zone block device write ordering control does not dependanymore on mq-deadline and zone write locking, there is no need to forceselect the mq-deadline scheduler when CONFIG_BLK_DEV_ZONED is enabled.Signed-off-by: Damien Le Moal &lt;dlemoal@kernel.org&gt;Reviewed-by: Bart Van Assche &lt;bvanassche@acm.org&gt;Reviewed-by: Hannes Reinecke &lt;hare@suse.de&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Tested-by: Hans Holmberg &lt;hans.holmberg@wdc.com&gt;Tested-by: Dennis Maisenbacher &lt;dennis.maisenbacher@wdc.com&gt;Reviewed-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;Link: https://lore.kernel.org/r/20240408014128.205141-28-dlemoal@kernel.orgSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Mon, 08 Apr 2024 01:41:27 +0000</pubDate>
        <dc:creator>Damien Le Moal &lt;dlemoal@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>d9f1439a - block: Move zone related debugfs attribute to blk-zoned.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#d9f1439a</link>
        <description>block: Move zone related debugfs attribute to blk-zoned.cblock/blk-mq-debugfs-zone.c contains a single debugfs attributefunction. Defining this outside of block/blk-zoned.c does not reallyhelp in any way, so move this zone related debugfs attribute toblock/blk-zoned.c and delete block/blk-mq-debugfs-zone.c.Signed-off-by: Damien Le Moal &lt;dlemoal@kernel.org&gt;Reviewed-by: Hannes Reinecke &lt;hare@suse.de&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Bart Van Assche &lt;bvanassche@acm.org&gt;Tested-by: Hans Holmberg &lt;hans.holmberg@wdc.com&gt;Tested-by: Dennis Maisenbacher &lt;dennis.maisenbacher@wdc.com&gt;Reviewed-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;Link: https://lore.kernel.org/r/20240408014128.205141-25-dlemoal@kernel.orgSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Mon, 08 Apr 2024 01:41:24 +0000</pubDate>
        <dc:creator>Damien Le Moal &lt;dlemoal@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>ed5cc702 - block: Add config option to not allow writing to mounted devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#ed5cc702</link>
        <description>block: Add config option to not allow writing to mounted devicesWriting to mounted devices is dangerous and can lead to filesystemcorruption as well as crashes. Furthermore syzbot comes with more andmore involved examples how to corrupt block device under a mountedfilesystem leading to kernel crashes and reports we can do nothingabout. Add tracking of writers to each block device and a kernel cmdlineargument which controls whether other writeable opens to block devicesopen with BLK_OPEN_RESTRICT_WRITES flag are allowed. We will makefilesystems use this flag for used devices.Note that this effectively only prevents modification of the particularblock device&apos;s page cache by other writers. The actual device contentcan still be modified by other means - e.g. by issuing direct scsicommands, by doing writes through devices lower in the storage stack(e.g. in case loop devices, DM, or MD are involved) etc. But blockingdirect modifications of the block device page cache is enough to givefilesystems a chance to perform data validation when loading data fromthe underlying storage and thus prevent kernel crashes.Syzbot can use this cmdline argument option to avoid uninterestingcrashes. Also users whose userspace setup does not need writing tomounted block devices can set this option for hardening.Link: https://lore.kernel.org/all/60788e5d-5c7c-1142-e554-c21d709acfd9@linaro.orgSigned-off-by: Jan Kara &lt;jack@suse.cz&gt;Link: https://lore.kernel.org/r/20231101174325.10596-3-jack@suse.czReviewed-by: Jens Axboe &lt;axboe@kernel.dk&gt;Signed-off-by: Christian Brauner &lt;brauner@kernel.org&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Wed, 01 Nov 2023 17:43:08 +0000</pubDate>
        <dc:creator>Jan Kara &lt;jack@suse.cz&gt;</dc:creator>
    </item>
<item>
        <title>ec8cf230 - powerpc/pseries: PLPKS SED Opal keystore support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#ec8cf230</link>
        <description>powerpc/pseries: PLPKS SED Opal keystore supportDefine operations for SED Opal to read/write keysfrom POWER LPAR Platform KeyStore(PLPKS). This allowsnon-volatile storage of SED Opal keys.Signed-off-by: Greg Joyce &lt;gjoyce@linux.vnet.ibm.com&gt;Reviewed-by: Jonathan Derrick &lt;jonathan.derrick@linux.dev&gt;Link: https://lore.kernel.org/r/20231004201957.1451669-4-gjoyce@linux.vnet.ibm.comSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Wed, 04 Oct 2023 20:19:57 +0000</pubDate>
        <dc:creator>Greg Joyce &lt;gjoyce@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>3bfeb612 - block: sed-opal: keyring support for SED keys</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#3bfeb612</link>
        <description>block: sed-opal: keyring support for SED keysExtend the SED block driver so it can alternativelyobtain a key from a sed-opal kernel keyring. The SEDioctls will indicate the source of the key, eitherdirectly in the ioctl data or from the keyring.This allows the use of SED commands in scripts such asudev scripts so that drives may be automatically unlockedas they become available.Signed-off-by: Greg Joyce &lt;gjoyce@linux.vnet.ibm.com&gt;Reviewed-by: Jonathan Derrick &lt;jonathan.derrick@linux.dev&gt;Acked-by: Jarkko Sakkinen &lt;jarkko@kernel.org&gt;Link: https://lore.kernel.org/r/20230721211534.3437070-4-gjoyce@linux.vnet.ibm.comSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Fri, 21 Jul 2023 21:15:34 +0000</pubDate>
        <dc:creator>Greg Joyce &lt;gjoyce@linux.vnet.ibm.com&gt;</dc:creator>
    </item>
<item>
        <title>487c607d - block: use iomap for writes to block devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#487c607d</link>
        <description>block: use iomap for writes to block devicesUse iomap in buffer_head compat mode to write to block devices.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Luis Chamberlain &lt;mcgrof@kernel.org&gt;Reviewed-by: Pankaj Raghav &lt;p.raghav@samsung.com&gt;Reviewed-by: Hannes Reinecke &lt;hare@suse.de&gt;Reviewed-by: Johannes Thumshirn &lt;johannes.thumshirn@wdc.com&gt;Reviewed-by: Christian Brauner &lt;brauner@kernel.org&gt;Link: https://lore.kernel.org/r/20230801172201.1923299-6-hch@lst.deSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Tue, 01 Aug 2023 17:22:00 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>2c275afe - block: make blkcg_punt_bio_submit optional</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#2c275afe</link>
        <description>block: make blkcg_punt_bio_submit optionalGuard all the code to punt bios to a per-cgroup submission helper by anew CONFIG_BLK_CGROUP_PUNT_BIO symbol that is selected by btrfs.This way non-btrfs kernel builds don&apos;t need to have this code.Reviewed-by: Jens Axboe &lt;axboe@kernel.dk&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: David Sterba &lt;dsterba@suse.com&gt;Signed-off-by: David Sterba &lt;dsterba@suse.com&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Mon, 27 Mar 2023 00:49:53 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>edde9e70 - blk-mq-rdma: remove queue mapping helper for rdma devices</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#edde9e70</link>
        <description>blk-mq-rdma: remove queue mapping helper for rdma devicesNo rdma device exposes its irq vectors affinity today. So the onlymapping that we have left, is the default blk_mq_map_queues, whichwe fallback to anyways. Also fixup the only consumer of this helper(nvme-rdma).Remove this now dead code.Signed-off-by: Sagi Grimberg &lt;sagi@grimberg.me&gt;Acked-by: Keith Busch &lt;kbusch@kernel.org&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Wed, 22 Mar 2023 12:37:03 +0000</pubDate>
        <dc:creator>Sagi Grimberg &lt;sagi@grimberg.me&gt;</dc:creator>
    </item>
<item>
        <title>8f0d196e - block: remove obsolete config BLOCK_COMPAT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#8f0d196e</link>
        <description>block: remove obsolete config BLOCK_COMPATBefore commit bdc1ddad3e5f (&quot;compat_ioctl: block: moveblkdev_compat_ioctl() into ioctl.c&quot;), the config BLOCK_COMPAT was used toinclude compat_ioctl.c into the kernel build. With this commit, the codeis moved into ioctl.c and included with the config COMPAT. So, since then,the config BLOCK_COMPAT has no effect and any further purpose.Remove this obsolete config BLOCK_COMPAT.Signed-off-by: Lukas Bulwahn &lt;lukas.bulwahn@gmail.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Link: https://lore.kernel.org/r/20230316111630.4897-1-lukas.bulwahn@gmail.comSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Thu, 16 Mar 2023 11:16:30 +0000</pubDate>
        <dc:creator>Lukas Bulwahn &lt;lukas.bulwahn@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b2b50d57 - block: Remove &quot;select SRCU&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#b2b50d57</link>
        <description>block: Remove &quot;select SRCU&quot;Now that the SRCU Kconfig option is unconditionally selected, there isno longer any point in selecting it.  Therefore, remove the &quot;select SRCU&quot;Kconfig statements.Signed-off-by: Paul E. McKenney &lt;paulmck@kernel.org&gt;Cc: Jens Axboe &lt;axboe@kernel.dk&gt;Cc: linux-block@vger.kernel.orgSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Thu, 05 Jan 2023 00:37:53 +0000</pubDate>
        <dc:creator>Paul E. McKenney &lt;paulmck@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b9a1c179 - block: remove &quot;select BLK_RQ_IO_DATA_LEN&quot; from BLK_CGROUP_IOCOST dependency</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#b9a1c179</link>
        <description>block: remove &quot;select BLK_RQ_IO_DATA_LEN&quot; from BLK_CGROUP_IOCOST dependencyThe configuration item BLK_RQ_IO_DATA_LEN is not declared in the kernel.Select BLK_RQ_IO_DATA_LEN is meaningless which could be removed.Signed-off-by: Ying Sun &lt;sunying@nj.iscas.ac.cn&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Link: https://lore.kernel.org/r/20220629062409.19458-1-sunying@nj.iscas.ac.cnSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Wed, 29 Jun 2022 06:24:09 +0000</pubDate>
        <dc:creator>Ying Sun &lt;sunying@nj.iscas.ac.cn&gt;</dc:creator>
    </item>
<item>
        <title>a7d4383f - block: add pi for extended integrity</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#a7d4383f</link>
        <description>block: add pi for extended integrityThe NVMe specification defines new data integrity formats beyond thet10 tuple. Add support for the specification defined CRC64 formats,assuming the reference tag does not need to be split with the &quot;storagetag&quot;.Cc: Hannes Reinecke &lt;hare@suse.de&gt;Cc: &quot;Martin K. Petersen&quot; &lt;martin.petersen@oracle.com&gt;Signed-off-by: Keith Busch &lt;kbusch@kernel.org&gt;Reviewed-by: Martin K. Petersen &lt;martin.petersen@oracle.com&gt;Link: https://lore.kernel.org/r/20220303201312.3255347-8-kbusch@kernel.orgSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Thu, 03 Mar 2022 20:13:11 +0000</pubDate>
        <dc:creator>Keith Busch &lt;kbusch@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>451f0b6f - block: default BLOCK_LEGACY_AUTOLOAD to y</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#451f0b6f</link>
        <description>block: default BLOCK_LEGACY_AUTOLOAD to yAs Luis reported, losetup currently doesn&apos;t properly create the loopdevice without this if the device node already exists because oldscripts created it manually.  So default to y for now and remove theaggressive removal schedule.Reported-by: Luis Chamberlain &lt;mcgrof@kernel.org&gt;Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Chaitanya Kulkarni &lt;kch@nvidia.com&gt;Link: https://lore.kernel.org/r/20220225181440.1351591-1-hch@lst.deSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Fri, 25 Feb 2022 18:14:40 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>248c7933 - blk-mq: make the blk-mq stacking code optional</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#248c7933</link>
        <description>blk-mq: make the blk-mq stacking code optionalThe code to stack blk-mq drivers is only used by dm-multipath, andwill preferably stay that way.  Make it optional and only selectedby device mapper, so that the buildbots more easily catch abuseslike the one that slipped in in the ufs driver in the last mergedwindow.  Another positive side effects is that kernel builds withoutdevice mapper shrink a little bit as well.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Mike Snitzer &lt;snitzer@redhat.com&gt;Link: https://lore.kernel.org/r/20220215100540.3892965-2-hch@lst.deSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Tue, 15 Feb 2022 10:05:36 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>fbdee71b - block: deprecate autoloading based on dev_t</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#fbdee71b</link>
        <description>block: deprecate autoloading based on dev_tMake the legacy dev_t based autoloading optional and add a deprecationwarning.  This kind of autoloading has ceased to be useful about 20 yearsago.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Link: https://lore.kernel.org/r/20220104071647.164918-1-hch@lst.deSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Tue, 04 Jan 2022 07:16:47 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>5ef16305 - block: only build the icq tracking code when needed</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#5ef16305</link>
        <description>block: only build the icq tracking code when neededOnly bfq needs to code to track icq, so make it conditional.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Reviewed-by: Jan Kara &lt;jack@suse.cz&gt;Link: https://lore.kernel.org/r/20211209063131.18537-12-hch@lst.deSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Thu, 09 Dec 2021 06:31:31 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>b8b98a62 - block: move menu &quot;Partition type&quot; to block/partitions/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/block/Kconfig#b8b98a62</link>
        <description>block: move menu &quot;Partition type&quot; to block/partitions/KconfigMove the menu to the relevant place.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;Link: https://lore.kernel.org/r/20210927140000.866249-4-masahiroy@kernel.orgSigned-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;

            List of files:
            /linux-6.15/block/Kconfig</description>
        <pubDate>Mon, 27 Sep 2021 13:59:59 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
