<?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>cccf6ee0 - ACPI: HED: Always initialize before evged</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#cccf6ee0</link>
        <description>ACPI: HED: Always initialize before evgedWhen the HED driver is built-in, it initializes after evged because theyboth are at the same initcall level, so the initialization orderingdepends on the Makefile order.  However, this prevents RAS recordscoming in between the evged driver initialization and the HED driverinitialization from being handled.If the number of such RAS records is above the APEI HEST error sourcenumber, the HEST resources may be exhausted, and that may affectsubsequent RAS error reporting.To fix this issue, change the initcall level of HED to subsys_initcalland prevent the driver from being built as a module by changing ACPI_HEDin Kconfig from &quot;tristate&quot; to &quot;bool&quot;.Signed-off-by: Xiaofei Tan &lt;tanxiaofei@huawei.com&gt;Link: https://patch.msgid.link/20250212063408.927666-1-tanxiaofei@huawei.com[ rjw: Changelog edits ]Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Wed, 12 Feb 2025 06:34:08 +0000</pubDate>
        <dc:creator>Xiaofei Tan &lt;tanxiaofei@huawei.com&gt;</dc:creator>
    </item>
<item>
        <title>0674188f - ACPI: EC: Enable EC support on LoongArch by default</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#0674188f</link>
        <description>ACPI: EC: Enable EC support on LoongArch by defaultCommit a6021aa24f6417416d933 (&quot;ACPI: EC: make EC support compile-timeconditional&quot;) only enable ACPI_EC on X86 by default, but the embeddedcontroller is also widely used on LoongArch laptops so we also enableACPI_EC for LoongArch.The laptop driver cannot work without EC, so also update the dependencyof LOONGSON_LAPTOP to let it depend on APCI_EC.Fixes: a6021aa24f6417416d933 (&quot;ACPI: EC: make EC support compile-time conditional&quot;)Reported-by: Xiaotian Wu &lt;wuxiaotian@loongson.cn&gt;Tested-by: Binbin Zhou &lt;zhoubinbin@loongson.cn&gt;Signed-off-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;Link: https://patch.msgid.link/20241217073704.3339587-1-chenhuacai@loongson.cn[ rjw: Added Fixes: ]Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Tue, 17 Dec 2024 07:37:04 +0000</pubDate>
        <dc:creator>Huacai Chen &lt;chenhuacai@loongson.cn&gt;</dc:creator>
    </item>
<item>
        <title>a6021aa2 - ACPI: EC: make EC support compile-time conditional</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#a6021aa2</link>
        <description>ACPI: EC: make EC support compile-time conditionalThe embedded controller code is mainly used on x86 laptops and cannotwork without PC style I/O port access.Make this a user-visible configuration option that is default enabledon x86 but otherwise disabled, and that can never be enabled unlessCONFIG_HAS_IOPORT is also available.The empty stubs in internal.h help ignore the EC code in configurationsthat don&apos;t support it. In order to see those stubs, the sbshc code alsohas to include this header and drop duplicate declarations.All the direct callers of ec_read/ec_write already had an x86dependency and now also need to depend on APCI_EC.Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: Guenter Roeck &lt;linux@roeck-us.net&gt;Acked-by: Hans de Goede &lt;hdegoede@redhat.com&gt;Link: https://patch.msgid.link/20241011061948.3211423-1-arnd@kernel.org[ rjw: Subject edits ]Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Fri, 11 Oct 2024 06:18:17 +0000</pubDate>
        <dc:creator>Arnd Bergmann &lt;arnd@arndb.de&gt;</dc:creator>
    </item>
<item>
        <title>d0bb0b60 - LoongArch: Enable ACPI BGRT handling</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#d0bb0b60</link>
        <description>LoongArch: Enable ACPI BGRT handlingAdd ACPI BGRT support on LoongArch so it can display image provied byacpi table at boot stage and switch to graphical UI smoothly.Signed-off-by: Bibo Mao &lt;maobibo@loongson.cn&gt;Signed-off-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Tue, 24 Sep 2024 07:32:06 +0000</pubDate>
        <dc:creator>Bibo Mao &lt;maobibo@loongson.cn&gt;</dc:creator>
    </item>
<item>
        <title>82b8acc0 - ACPI: NHLT: Introduce API for the table</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#82b8acc0</link>
        <description>ACPI: NHLT: Introduce API for the tableThe table is composed of a range of endpoints with each describingaudio formats they support. Most of the operations involve iteratingover elements of the table and filtering them. Simplify the process byimplementing range of getters.While the acpi_nhlt_endpoint_mic_count() stands out a bit, it is acritical component for any AudioDSP driver to know how many digitalmicrophones it is dealing with.Signed-off-by: Cezary Rojewski &lt;cezary.rojewski@intel.com&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Tue, 19 Mar 2024 08:30:16 +0000</pubDate>
        <dc:creator>Cezary Rojewski &lt;cezary.rojewski@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>359df7c5 - ACPI: Enable ACPI_PROCESSOR for RISC-V</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#359df7c5</link>
        <description>ACPI: Enable ACPI_PROCESSOR for RISC-VThe ACPI processor driver is not currently enabled for RISC-V.This is required to enable CPU related functionalities likeLPI and CPPC. Hence, enable ACPI_PROCESSOR for RISC-V.Signed-off-by: Sunil V L &lt;sunilvl@ventanamicro.com&gt;Reviewed-by: Andrew Jones &lt;ajones@ventanamicro.com&gt;Acked-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;Link: https://lore.kernel.org/r/20240118062930.245937-4-sunilvl@ventanamicro.comSigned-off-by: Palmer Dabbelt &lt;palmer@rivosinc.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Thu, 18 Jan 2024 06:29:30 +0000</pubDate>
        <dc:creator>Sunil V L &lt;sunilvl@ventanamicro.com&gt;</dc:creator>
    </item>
<item>
        <title>0cc46f1a - ACPI: Drop the custom_method debugfs interface</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#0cc46f1a</link>
        <description>ACPI: Drop the custom_method debugfs interfaceThe ACPI custom_method debugfs interface is security-sensitive andconcurrent access to it is broken [1].Moreover, the recipe for preparing a customized version of a givencontrol method has changed at one point due to ACPICA changes, whichhas not been reflected in its documentation, so whoever used it beforehas had to adapt and it had gone unnoticed for a long time.This interface was a bad idea to start with and its implementation isfragile at the design level.  It&apos;s been always conceptually questionable,problematic from the security standpoint and implemented poorly.Patches fixing its most apparent functional issues (for example, [2]) don&apos;tactually address much of the above.Granted, at the time it was introduced, there was no alternative, butthere is the AML debugger in the kernel now and there is the configfsinterface allowing custom ACPI tables to be loaded.  The former can beused for extensive AML debugging and the latter can be use for testingnew AML. [3]Accordingly, drop custom_method along with its (outdated anyway)documentation.Link: https://lore.kernel.org/linux-acpi/20221227063335.61474-1-zh.nvgt@gmail.com/ # [1]Link: https://lore.kernel.org/linux-acpi/20231111132402.4142-1-shiqiang.deng213@gmail.com/ [2]Link: https://stackoverflow.com/questions/62849113/how-to-unload-an-overlay-loaded-using-acpi-config-sysfs # [3]Reported-by: Hang Zhang &lt;zh.nvgt@gmail.com&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;Reviewed-by: Zhang Rui &lt;rui.zhang@intel.com&gt;Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Fri, 16 Feb 2024 16:38:55 +0000</pubDate>
        <dc:creator>Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>cd14b018 - treewide: replace or remove redundant def_bool in Kconfig files</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#cd14b018</link>
        <description>treewide: replace or remove redundant def_bool in Kconfig files&apos;def_bool X&apos; is a shorthand for &apos;bool&apos; plus &apos;default X&apos;.&apos;def_bool&apos; is redundant where &apos;bool&apos; is already present, so &apos;def_bool X&apos;can be replaced with &apos;default X&apos;, or removed if X is &apos;n&apos;.Signed-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Sun, 11 Feb 2024 12:48:08 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>a02f66bb - ACPI: Move ACPI_HOTPLUG_CPU to be disabled on arm64 and riscv</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#a02f66bb</link>
        <description>ACPI: Move ACPI_HOTPLUG_CPU to be disabled on arm64 and riscvNeither arm64 nor riscv support physical hotadd of CPUs that were notpresent at boot. For arm64 much of the platform description is in statictables which do not have update methods. arm64 does support HOTPLUG_CPU,which is backed by a firmware interface to turn CPUs on and off.acpi_processor_hotadd_init() and acpi_processor_remove() are for addingand removing CPUs that were not present at boot. arm64 systems that do thisare not supported as there is currently insufficient information in theplatform description. (e.g. did the GICR get removed too?)arm64 currently relies on the MADT enabled flag check in map_gicc_mpidr()to prevent CPUs that were not described as present at boot from beingadded to the system. Similarly, riscv relies on the same check inmap_rintc_hartid(). Both architectures also rely on the weak &apos;always fails&apos;definitions of acpi_map_cpu() and arch_register_cpu().Subsequent changes will redefine ACPI_HOTPLUG_CPU as making possibleCPUs present. Neither arm64 nor riscv support this.Disable ACPI_HOTPLUG_CPU for arm64 and riscv by removing &apos;default y&apos; andselecting it on the other three ACPI architectures. This allows the weakdefinitions of some symbols to be removed.Signed-off-by: James Morse &lt;james.morse@arm.com&gt;Reviewed-by: Shaoqin Huang &lt;shahuang@redhat.com&gt;Reviewed-by: Gavin Shan &lt;gshan@redhat.com&gt;Signed-off-by: &quot;Russell King (Oracle)&quot; &lt;rmk+kernel@armlinux.org.uk&gt;Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Link: https://lore.kernel.org/r/E1r5R31-00Csyt-Jq@rmk-PC.armlinux.org.ukSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Tue, 21 Nov 2023 13:44:15 +0000</pubDate>
        <dc:creator>James Morse &lt;james.morse@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>f4750798 - thermal: ACPI: Move the ACPI thermal library to drivers/acpi/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#f4750798</link>
        <description>thermal: ACPI: Move the ACPI thermal library to drivers/acpi/The ACPI thermal library contains functions that can be used toretrieve trip point temperature values through the platform firmwarefor various types of trip points.  Each of these functions basicallyevaluates a specific ACPI object, checks if the value produced by itis reasonable and returns it (or THERMAL_TEMP_INVALID if anythingfails).It made sense to hold it in drivers/thermal/ so long as it was only usedby the code in that directory, but since it is also going to be used bythe ACPI thermal driver located in drivers/acpi/, move it to the latterin order to keep the code related to evaluating ACPI objects defined inthe specification proper together.No intentional functional impact.Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Tue, 17 Oct 2023 20:05:23 +0000</pubDate>
        <dc:creator>Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>a103f466 - acpi: Move common tables helper functions to common lib</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#a103f466</link>
        <description>acpi: Move common tables helper functions to common libSome of the routines in ACPI driver/acpi/tables.c can be shared withparsing CDAT. CDAT is a device-provided data structure that is formattedsimilar to a platform provided ACPI table. CDAT is used by CXL and canexist on platforms that do not use ACPI. Split out the common routinefrom ACPI to accommodate platforms that do not support ACPI and move thatto /lib. The common routines can be built outside of ACPI ifFIRMWARE_TABLES is selected.Link: https://lore.kernel.org/linux-cxl/CAJZ5v0jipbtTNnsA0-o5ozOk8ZgWnOg34m34a9pPenTyRLj=6A@mail.gmail.com/Suggested-by: &quot;Rafael J. Wysocki&quot; &lt;rafael@kernel.org&gt;Reviewed-by: Hanjun Guo &lt;guohanjun@huawei.com&gt;Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Signed-off-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Acked-by: &quot;Rafael J. Wysocki&quot; &lt;rafael.j.wysocki@intel.com&gt;Link: https://lore.kernel.org/r/169713683430.2205276.17899451119920103445.stgit@djiang5-mobl3Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Thu, 12 Oct 2023 18:53:54 +0000</pubDate>
        <dc:creator>Dave Jiang &lt;dave.jiang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>cf8e8658 - arch: Remove Itanium (IA-64) architecture</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#cf8e8658</link>
        <description>arch: Remove Itanium (IA-64) architectureThe Itanium architecture is obsolete, and an informal survey [0] revealsthat any residual use of Itanium hardware in production is mostly HP-UXor OpenVMS based. The use of Linux on Itanium appears to be limited toenthusiasts that occasionally boot a fresh Linux kernel to see whetherthings are still working as intended, and perhaps to churn out somedistro packages that are rarely used in practice.None of the original companies behind Itanium still produce or supportany hardware or software for the architecture, and it is listed as&apos;Orphaned&apos; in the MAINTAINERS file, as apparently, none of the engineersthat contributed on behalf of those companies (nor anyone else, for thatmatter) have been willing to support or maintain the architectureupstream or even be responsible for applying the odd fix. The Intelfirmware team removed all IA-64 support from the Tianocore/EDK2reference implementation of EFI in 2018. (Itanium is the originalarchitecture for which EFI was developed, and the way Linux supports itdeviates significantly from other architectures.) Some distros, such asDebian and Gentoo, still maintain [unofficial] ia64 ports, but many havedropped support years ago.While the argument is being made [1] that there is a &apos;for the commongood&apos; angle to being able to build and run existing projects such as theGrid Community Toolkit [2] on Itanium for interoperability testing, thefact remains that none of those projects are known to be deployed onLinux/ia64, and very few people actually have access to such a system inthe first place. Even if there were ways imaginable in which Linux/ia64could be put to good use today, what matters is whether anyone isactually doing that, and this does not appear to be the case.There are no emulators widely available, and so boot testing Itanium isgenerally infeasible for ordinary contributors. GCC still supports IA-64but its compile farm [3] no longer has any IA-64 machines. GLIBC wouldlike to get rid of IA-64 [4] too because it would permit some overduecode cleanups. In summary, the benefits to the ecosystem of having IA-64be part of it are mostly theoretical, whereas the maintenance overheadof keeping it supported is real.So let&apos;s rip off the band aid, and remove the IA-64 arch code entirely.This follows the timeline proposed by the Debian/ia64 maintainer [5],which removes support in a controlled manner, leaving IA-64 in a knowngood state in the most recent LTS release. Other projects will followonce the kernel support is removed.[0] https://lore.kernel.org/all/CAMj1kXFCMh_578jniKpUtx_j8ByHnt=s7S+yQ+vGbKt9ud7+kQ@mail.gmail.com/[1] https://lore.kernel.org/all/0075883c-7c51-00f5-2c2d-5119c1820410@web.de/[2] https://gridcf.org/gct-docs/latest/index.html[3] https://cfarm.tetaneutral.net/machines/list/[4] https://lore.kernel.org/all/87bkiilpc4.fsf@mid.deneb.enyo.de/[5] https://lore.kernel.org/all/ff58a3e76e5102c94bb5946d99187b358def688a.camel@physik.fu-berlin.de/Acked-by: Tony Luck &lt;tony.luck@intel.com&gt;Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Thu, 20 Oct 2022 13:54:33 +0000</pubDate>
        <dc:creator>Ard Biesheuvel &lt;ardb@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>5894cf57 - acpi/prmt: Use EFI runtime sandbox to invoke PRM handlers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#5894cf57</link>
        <description>acpi/prmt: Use EFI runtime sandbox to invoke PRM handlersInstead of bypassing the kernel&apos;s adaptation layer for performing EFIruntime calls, wire up ACPI PRM handling into it. This means these callscan no longer occur concurrently with EFI runtime calls, and will bemade from the EFI runtime workqueue. It also means any page faultsoccurring during PRM handling will be identified correctly asoriginating in firmware code.Acked-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Sun, 02 Jul 2023 09:57:34 +0000</pubDate>
        <dc:creator>Ard Biesheuvel &lt;ardb@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>f6f0c9a7 - LoongArch: Add SMT (Simultaneous Multi-Threading) support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#f6f0c9a7</link>
        <description>LoongArch: Add SMT (Simultaneous Multi-Threading) supportLoongson-3A6000 has SMT (Simultaneous Multi-Threading) support, eachphysical core has two logical cores (threads). This patch add SMT probeand scheduler support via ACPI PPTT.If SCHED_SMT enabled, Loongson-3A6000 is treated as 4 cores, 8 threads;If SCHED_SMT disabled, Loongson-3A6000 is treated as 8 cores, 8 threads.Remove smp_num_siblings to support HMP (Heterogeneous Multi-Processing).Signed-off-by: Liupu Wang &lt;wangliupu@loongson.cn&gt;Signed-off-by: Huacai Chen &lt;chenhuacai@loongson.cn&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Thu, 29 Jun 2023 12:58:43 +0000</pubDate>
        <dc:creator>Huacai Chen &lt;chenhuacai@loongson.cn&gt;</dc:creator>
    </item>
<item>
        <title>e81c782c - ACPI: Implement a generic FFH Opregion handler</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#e81c782c</link>
        <description>ACPI: Implement a generic FFH Opregion handlerThis registers the FFH OpRegion handler before ACPI tables areloaded. The platform support for the same is checked via Platform-WideOSPM Capabilities(OSC) before registering the OpRegion handler.It relies on the special context data passed to offset and the length.However the interpretation of the values is platform/architecturespecific. This generic handler just passed all the information tothe platform/architecture specific callback. It also implements thedefault callbacks which return as not supported.Signed-off-by: Sudeep Holla &lt;sudeep.holla@arm.com&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Thu, 10 Nov 2022 13:45:04 +0000</pubDate>
        <dc:creator>Sudeep Holla &lt;sudeep.holla@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>c2465f95 - ACPI: Enable FPDT on arm64</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#c2465f95</link>
        <description>ACPI: Enable FPDT on arm64FPDT provides some boot timing records useful for analyzingparts of the UEFI boot stack. Given the existing code workson arm64, and allows reading the values without utilizing/dev/mem it seems like a good idea to turn it on.Signed-off-by: Jeremy Linton &lt;jeremy.linton@arm.com&gt;Acked-by: Sudeep Holla &lt;sudeep.holla@arm.com&gt;Link: https://lore.kernel.org/r/20221109174720.203723-1-jeremy.linton@arm.comSigned-off-by: Will Deacon &lt;will@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Wed, 09 Nov 2022 17:47:20 +0000</pubDate>
        <dc:creator>Jeremy Linton &lt;jeremy.linton@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>a97edbaa - ACPI: Kconfig: Drop link to https://01.org/linux-acpi</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#a97edbaa</link>
        <description>ACPI: Kconfig: Drop link to https://01.org/linux-acpiBecause the https://01.org/linux-acpi web site has become permanentlyinaccessible, drop the remaining link to it from the ACPI Kconfig.Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Mon, 26 Sep 2022 20:27:56 +0000</pubDate>
        <dc:creator>Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>d206cef0 - ACPI: docs: Drop useless DSDT override documentation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#d206cef0</link>
        <description>ACPI: docs: Drop useless DSDT override documentationBecause https://01.org/linux-acpi web site has become permanentlyinaccessible, the &quot;Overriding DSDT&quot; document in the kernel treepointing to it as the main source of information is useless (andthe config option name mentioned by it is incorrect), so drop itand drop the pointer to it from the ACPI Kconfig.Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Mon, 26 Sep 2022 20:20:03 +0000</pubDate>
        <dc:creator>Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>fe7aebb4 - ACPI: video: Add Nvidia WMI EC brightness control detection (v3)</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#fe7aebb4</link>
        <description>ACPI: video: Add Nvidia WMI EC brightness control detection (v3)On some new laptop designs a new Nvidia specific WMI interface is presentwhich gives info about panel brightness control and may allow controllingthe brightness through this interface when the embedded controller is usedfor brightness control.When this WMI interface is present and indicates that the EC is used,then this interface should be used for brightness control.Changes in v2:- Use the new shared nvidia-wmi-ec-backlight.h header for the  WMI firmware API definitions- ACPI_VIDEO can now be enabled on non X86 too,  adjust the Kconfig changes to match this.Changes in v3:- Use WMI_BRIGHTNESS_GUID defineAcked-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;Reviewed-by: Daniel Dadap &lt;ddadap@nvidia.com&gt;Signed-off-by: Hans de Goede &lt;hdegoede@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Sat, 04 Jun 2022 12:06:18 +0000</pubDate>
        <dc:creator>Hans de Goede &lt;hdegoede@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>e3435fff - ACPI: Move PRM config option under the main ACPI config</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/Kconfig#e3435fff</link>
        <description>ACPI: Move PRM config option under the main ACPI configCurrently PRM(Platform Runtime Mechanism) config option is listed alongwith the main ACPI (Advanced Configuration and Power Interface) optionat the same level. On ARM64 platforms unlike x86, ACPI option is listedat the topmost level of configuration menu. It is rather very confusingto see PRM option also listed along with ACPI in the topmost level.Move the same under ACPI config option. No functional change, just changesthe level of visibility of this option under the configuration menu.Signed-off-by: Sudeep Holla &lt;sudeep.holla@arm.com&gt;Acked-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/Kconfig</description>
        <pubDate>Tue, 28 Jun 2022 12:53:46 +0000</pubDate>
        <dc:creator>Sudeep Holla &lt;sudeep.holla@arm.com&gt;</dc:creator>
    </item>
</channel>
</rss>
