<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/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>9d2ed026f031f764e9450ac9aada2f46bc977397 - Merge tag &apos;sysctl-7.03-rc1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/sysctl/sysctl</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#9d2ed026f031f764e9450ac9aada2f46bc977397</link>
        <description>Merge tag &apos;sysctl-7.03-rc1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/sysctl/sysctlPull sysctl updates from Joel Granados: - Fix kernel-doc warnings by adjusting in file documentation - Consolidate do_proc_* function into do_proc_vec   Consolidate three slightly different implementations of applying a   converter on all elements of a vector. Fixes to this function now   propagate to the three types. - Replace CONFIG_PROC_SYSCTL with CONFIG_SYSCTL (they were the same)   and restrict cad_pid modifications to global root (GLOBAL_ROOT_UID)* tag &apos;sysctl-7.03-rc1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/sysctl/sysctl:  sysctl: remove CONFIG_PROC_SYSCTL, it just mirrors CONFIG_SYSCTL  sysctl: move the &quot;cad_pid&quot; entry from pid_table[] to kern_reboot_table[]  sysctl: repair some kernel-doc comments  sysctl: add Returns: kernel-doc for all functions  sysctl: Update API function documentation  sysctl: Rename proc_doulongvec_minmax_conv to proc_doulongvec_conv  sysctl: Group proc_handler declarations and document  sysctl: Replace do_proc_do{int,ulong,uint}vec with do_proc_vec  sysctl: Add negp parameter to douintvec converter functions  sysctl: Move default converter assignment out of do_proc_dointvec

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Thu, 20 Aug 2026 17:46:41 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>8d75c338f0bcecaa6c9af67f86c176b67b6acf3e - sysctl: remove CONFIG_PROC_SYSCTL, it just mirrors CONFIG_SYSCTL</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#8d75c338f0bcecaa6c9af67f86c176b67b6acf3e</link>
        <description>sysctl: remove CONFIG_PROC_SYSCTL, it just mirrors CONFIG_SYSCTLCONFIG_SYSCTL used to make sense as a separate hidden bool before commit61a47c1ad3a4 (&quot;sysctl: Remove the sysctl system call&quot;); it was selectedby both CONFIG_SYSCTL_SYSCALL and CONFIG_PROC_SYSCTL.Today CONFIG_PROC_SYSCTL is the only selector, so the two are alwaysequal. Kill the hidden bool, rename the PROC_SYSCTL prompt to SYSCTL,and s/CONFIG_PROC_SYSCTL/CONFIG_SYSCTL/ tree-wide.Signed-off-by: Oleg Nesterov &lt;oleg@redhat.com&gt;Signed-off-by: Joel Granados &lt;joel.granados@kernel.org&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Mon, 27 Jul 2026 16:47:22 +0200</pubDate>
        <dc:creator>Oleg Nesterov &lt;oleg@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>1260ed77798502de9c98020040d2995008de10cc - Merge drm/drm-fixes into drm-misc-fixes</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#1260ed77798502de9c98020040d2995008de10cc</link>
        <description>Merge drm/drm-fixes into drm-misc-fixesBackmerging to get updates from v6.15-rc1.Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Tue, 08 Apr 2025 10:15:47 +0200</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>946661e3bef8efa11ba8079d4ebafe6fc3b0aaad - Merge branch &apos;next&apos; into for-linus</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#946661e3bef8efa11ba8079d4ebafe6fc3b0aaad</link>
        <description>Merge branch &apos;next&apos; into for-linusPrepare input updates for 6.15 merge window.

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Sat, 05 Apr 2025 08:04:35 +0200</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>0b119045b79a672bc6d8f18641c60fc8ce1b4585 - Merge tag &apos;v6.14-rc4&apos; into next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#0b119045b79a672bc6d8f18641c60fc8ce1b4585</link>
        <description>Merge tag &apos;v6.14-rc4&apos; into nextSync up with the mainline.

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Wed, 26 Feb 2025 01:03:25 +0100</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>9e676a024fa1fa2bd8150c2d2ba85478280353bc - Merge tag &apos;v6.14-rc1&apos; into perf-tools-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#9e676a024fa1fa2bd8150c2d2ba85478280353bc</link>
        <description>Merge tag &apos;v6.14-rc1&apos; into perf-tools-nextTo get the various fixes in the current master.Signed-off-by: Namhyung Kim &lt;namhyung@kernel.org&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Wed, 05 Feb 2025 23:57:18 +0100</pubDate>
        <dc:creator>Namhyung Kim &lt;namhyung@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>0410c6121529409b08e81a77ae3ee58c657e2243 - Merge drm/drm-next into drm-xe-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#0410c6121529409b08e81a77ae3ee58c657e2243</link>
        <description>Merge drm/drm-next into drm-xe-nextSync to fix conlicts between drm-xe-next and drm-intel-next.Signed-off-by: Lucas De Marchi &lt;lucas.demarchi@intel.com&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Fri, 28 Feb 2025 15:54:14 +0100</pubDate>
        <dc:creator>Lucas De Marchi &lt;lucas.demarchi@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>93c7dd1b39444ebd5a6a98e56a363d7a4e646775 - Merge drm/drm-next into drm-misc-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#93c7dd1b39444ebd5a6a98e56a363d7a4e646775</link>
        <description>Merge drm/drm-next into drm-misc-nextBring rc1 to start the new release dev.Signed-off-by: Maxime Ripard &lt;mripard@kernel.org&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Thu, 06 Feb 2025 13:47:32 +0100</pubDate>
        <dc:creator>Maxime Ripard &lt;mripard@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>ea9f8f2b21795a5d80418a655bcb212d5b89e08f - Merge drm/drm-next into drm-intel-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#ea9f8f2b21795a5d80418a655bcb212d5b89e08f</link>
        <description>Merge drm/drm-next into drm-intel-nextSync with v6.14-rc1.Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Wed, 05 Feb 2025 18:12:37 +0100</pubDate>
        <dc:creator>Jani Nikula &lt;jani.nikula@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>c771600c6af14749609b49565ffb4cac2959710d - Merge drm/drm-next into drm-intel-gt-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#c771600c6af14749609b49565ffb4cac2959710d</link>
        <description>Merge drm/drm-next into drm-intel-gt-nextWe need4ba4f1afb6a9 (&quot;perf: Generic hotplug support for a PMU with a scope&quot;)in order to land a i915 PMU simplification and a fix. That landed in 6.12and we are stuck at 6.9 so lets bump things forward.Signed-off-by: Tvrtko Ursulin &lt;tursulin@ursulin.net&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Wed, 05 Feb 2025 10:29:14 +0100</pubDate>
        <dc:creator>Tvrtko Ursulin &lt;tursulin@ursulin.net&gt;</dc:creator>
    </item>
<item>
        <title>b3cc7428a32202936904b5b07cf9f135025bafd6 - Merge branch &apos;for-6.15/amd_sfh&apos; into for-linus</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#b3cc7428a32202936904b5b07cf9f135025bafd6</link>
        <description>Merge branch &apos;for-6.15/amd_sfh&apos; into for-linusFrom: Mario Limonciello &lt;mario.limonciello@amd.com&gt;Some platforms include a human presence detection (HPD) sensor. Whenenabled and a user is detected a wake event will be emitted from thesensor fusion hub that software can react to.Example use cases are &quot;wake from suspend on approach&quot; or to &quot;lockwhen leaving&quot;.This is currently enabled by default on supported systems, but userscan&apos;t control it. This essentially means that wake on approach isenabled which is a really surprising behavior to users that don&apos;texpect it.Instead of defaulting to enabled add a sysfs knob that users canuse to enable the feature if desirable and set it to disabled bydefault.

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Wed, 26 Mar 2025 13:42:07 +0100</pubDate>
        <dc:creator>Jiri Kosina &lt;jkosina@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>deee7487f5d495d0d9e5ab40d866d69ad524c46a - Merge tag &apos;for_linus&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#deee7487f5d495d0d9e5ab40d866d69ad524c46a</link>
        <description>Merge tag &apos;for_linus&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhostPull virtio updates from Michael Tsirkin: &quot;A small number of improvements all over the place:   - vdpa/octeon support for multiple interrupts   - virtio-pci support for error recovery   - vp_vdpa support for notification with data   - vhost/net fix to set num_buffers for spec compliance   - virtio-mem now works with kdump on s390  And small cleanups all over the place&quot;* tag &apos;for_linus&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost: (23 commits)  virtio_blk: Add support for transport error recovery  virtio_pci: Add support for PCIe Function Level Reset  vhost/net: Set num_buffers for virtio 1.0  vdpa/octeon_ep: read vendor-specific PCI capability  virtio-pci: define type and header for PCI vendor data  vdpa/octeon_ep: handle device config change events  vdpa/octeon_ep: enable support for multiple interrupts per device  vdpa: solidrun: Replace deprecated PCI functions  s390/kdump: virtio-mem kdump support (CONFIG_PROC_VMCORE_DEVICE_RAM)  virtio-mem: support CONFIG_PROC_VMCORE_DEVICE_RAM  virtio-mem: remember usable region size  virtio-mem: mark device ready before registering callbacks in kdump mode  fs/proc/vmcore: introduce PROC_VMCORE_DEVICE_RAM to detect device RAM ranges in 2nd kernel  fs/proc/vmcore: factor out freeing a list of vmcore ranges  fs/proc/vmcore: factor out allocating a vmcore range and adding it to a list  fs/proc/vmcore: move vmcore definitions out of kcore.h  fs/proc/vmcore: prefix all pr_* with &quot;vmcore:&quot;  fs/proc/vmcore: disallow vmcore modifications while the vmcore is open  fs/proc/vmcore: replace vmcoredd_mutex by vmcore_mutex  fs/proc/vmcore: convert vmcore_cb_lock into vmcore_mutex  ...

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Tue, 28 Jan 2025 00:26:06 +0100</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>c6a8239a9eddf38137797292ed75432957a37a14 - virtio-mem: support CONFIG_PROC_VMCORE_DEVICE_RAM</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#c6a8239a9eddf38137797292ed75432957a37a14</link>
        <description>virtio-mem: support CONFIG_PROC_VMCORE_DEVICE_RAMLet&apos;s implement the get_device_ram() vmcore callback, soarchitectures that select NEED_PROC_VMCORE_NEED_DEVICE_RAM, like s390soon, can include that memory in a crash dump.Merge ranges, and process ranges that might contain a mixture of pluggedand unplugged, to reduce the total number of ranges.Signed-off-by: David Hildenbrand &lt;david@redhat.com&gt;Message-Id: &lt;20241204125444.1734652-12-david@redhat.com&gt;Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Wed, 04 Dec 2024 13:54:42 +0100</pubDate>
        <dc:creator>David Hildenbrand &lt;david@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>7ad4d1f6e6ef967cd24c6275d8d4056045c019c1 - fs/proc/vmcore: introduce PROC_VMCORE_DEVICE_RAM to detect device RAM ranges in 2nd kernel</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#7ad4d1f6e6ef967cd24c6275d8d4056045c019c1</link>
        <description>fs/proc/vmcore: introduce PROC_VMCORE_DEVICE_RAM to detect device RAM ranges in 2nd kernels390 allocates+prepares the elfcore hdr in the dump (2nd) kernel, not inthe crashed kernel.RAM provided by memory devices such as virtio-mem can only be detectedusing the device driver; when vmcore_init() is called, these devicedrivers are usually not loaded yet, or the devices did not get probedyet. Consequently, on s390 these RAM ranges will not be included inthe crash dump, which makes the dump partially corrupt and isunfortunate.Instead of deferring the vmcore_init() call, to an (unclear?) later point,let&apos;s reuse the vmcore_cb infrastructure to obtain device RAM ranges asthe device drivers probe the device and get access to this information.Then, we&apos;ll add these ranges to the vmcore, adding more PT_LOADentries and updating the offsets+vmcore size.Use a separate Kconfig option to be set by an architecture to include thiscode only if the arch really needs it. Further, we&apos;ll make the configdepend on the relevant drivers (i.e., virtio_mem) once they implementsupport (next). The alternative of having a PROVIDE_PROC_VMCORE_DEVICE_RAMconfig option was dropped for now for simplicity.The current target use case is s390, which only creates an elf64elfcore, so focusing on elf64 is sufficient.Signed-off-by: David Hildenbrand &lt;david@redhat.com&gt;Message-Id: &lt;20241204125444.1734652-9-david@redhat.com&gt;Acked-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Wed, 04 Dec 2024 13:54:39 +0100</pubDate>
        <dc:creator>David Hildenbrand &lt;david@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>a23e1966932464e1c5226cb9ac4ce1d5fc10ba22 - Merge branch &apos;next&apos; into for-linus</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#a23e1966932464e1c5226cb9ac4ce1d5fc10ba22</link>
        <description>Merge branch &apos;next&apos; into for-linusPrepare input updates for 6.11 merge window.

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Mon, 15 Jul 2024 23:03:44 +0200</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>6f47c7ae8c7afaf9ad291d39f0d3974f191a7946 - Merge tag &apos;v6.9&apos; into next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#6f47c7ae8c7afaf9ad291d39f0d3974f191a7946</link>
        <description>Merge tag &apos;v6.9&apos; into nextSync up with the mainline to bring in the new cleanup API.

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Tue, 28 May 2024 06:37:18 +0200</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>60a2f25de7b8b785baee2932db932ae9a5b8c86d - Merge drm/drm-next into drm-intel-gt-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#60a2f25de7b8b785baee2932db932ae9a5b8c86d</link>
        <description>Merge drm/drm-next into drm-intel-gt-nextSome display refactoring patches are needed in order to allow conflict-less merging.Signed-off-by: Tvrtko Ursulin &lt;tursulin@ursulin.net&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Thu, 16 May 2024 09:33:01 +0200</pubDate>
        <dc:creator>Tvrtko Ursulin &lt;tursulin@ursulin.net&gt;</dc:creator>
    </item>
<item>
        <title>594ce0b8a998aa4d05827cd7c0d0dcec9a1e3ae2 - Merge topic branches &apos;clkdev&apos; and &apos;fixes&apos; into for-linus</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#594ce0b8a998aa4d05827cd7c0d0dcec9a1e3ae2</link>
        <description>Merge topic branches &apos;clkdev&apos; and &apos;fixes&apos; into for-linus

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Mon, 10 Jun 2024 13:03:21 +0200</pubDate>
        <dc:creator>Russell King (Oracle) &lt;rmk+kernel@armlinux.org.uk&gt;</dc:creator>
    </item>
<item>
        <title>79790b6818e96c58fe2bffee1b418c16e64e7b80 - Merge drm/drm-next into drm-xe-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#79790b6818e96c58fe2bffee1b418c16e64e7b80</link>
        <description>Merge drm/drm-next into drm-xe-nextBackmerging drm-next in order to get up-to-date and in particularto access commit 9ca5facd0400f610f3f7f71aeb7fc0b949a48c67.Signed-off-by: Thomas Hellstr&#246;m &lt;thomas.hellstrom@linux.intel.com&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Fri, 12 Apr 2024 15:14:25 +0200</pubDate>
        <dc:creator>Thomas Hellstr&#246;m &lt;thomas.hellstrom@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>3e5a516f3bf1a33f2bf219f570e9b5c031616f6a - Merge tag &apos;phy_dp_modes_6.10&apos; into msm-next-lumag</title>
        <link>http://kernelsources.org:8080/source/history/linux/fs/proc/Kconfig#3e5a516f3bf1a33f2bf219f570e9b5c031616f6a</link>
        <description>Merge tag &apos;phy_dp_modes_6.10&apos; into msm-next-lumagMerge DisplayPort subnode API in order to allow DisplayPort driver toconfigure the PHYs either to the DP or eDP mode, depending on hardwareconfiguration.Signed-off-by: Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;

            List of files:
            /linux/fs/proc/Kconfig</description>
        <pubDate>Mon, 08 Apr 2024 17:35:51 +0200</pubDate>
        <dc:creator>Dmitry Baryshkov &lt;dmitry.baryshkov@linaro.org&gt;</dc:creator>
    </item>
</channel>
</rss>
