<?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>12fb28ea - EINJ: Add CXL error type support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#12fb28ea</link>
        <description>EINJ: Add CXL error type supportMove CXL protocol error types from einj.c (now einj-core.c) to einj-cxl.c.einj-cxl.c implements the necessary handling for CXL protocol errorinjection and exposes an API for the CXL core to use said functionality,while also allowing the EINJ module to be built without CXL support.Because CXL error types targeting CXL 1.0/1.1 ports require specialhandling, only allow them to be injected through the new cxl debugfsinterface (next commit) and return an error when attempting to injectthrough the legacy interface.Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Signed-off-by: Ben Cheatham &lt;Benjamin.Cheatham@amd.com&gt;Link: https://lore.kernel.org/r/20240311142508.31717-3-Benjamin.Cheatham@amd.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Mon, 11 Mar 2024 14:25:06 +0000</pubDate>
        <dc:creator>Ben Cheatham &lt;Benjamin.Cheatham@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>255097c8 - ACPI / APEI: Switch NOTIFY_SEA to use the estatus queue</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#255097c8</link>
        <description>ACPI / APEI: Switch NOTIFY_SEA to use the estatus queueNow that the estatus queue can be used by more than one notificationmethod, we can move notifications that have NMI-like behaviour over.Switch NOTIFY_SEA over to use the estatus queue. This makes it behavein the same way as x86&apos;s NOTIFY_NMI.Remove Kconfig&apos;s ability to turn ACPI_APEI_SEA off if ACPI_APEI_GHESis selected. This roughly matches the x86 NOTIFY_NMI behaviour, and meanseach architecture has at least one user of the estatus-queue, meaning itdoesn&apos;t need guarding with ifdef.Signed-off-by: James Morse &lt;james.morse@arm.com&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Tue, 29 Jan 2019 18:48:48 +0000</pubDate>
        <dc:creator>James Morse &lt;james.morse@arm.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>7edda088 - acpi: apei: handle SEA notification type for ARMv8</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#7edda088</link>
        <description>acpi: apei: handle SEA notification type for ARMv8ARM APEI extension proposal added SEA (Synchronous External Abort)notification type for ARMv8.Add a new GHES error source handling function for SEA. If an errorsource&apos;s notification type is SEA, then this function can be registeredinto the SEA exception handler. That way GHES will parse and reportSEA exceptions when they occur.An SEA can interrupt code that had interrupts masked and is treated asan NMI. To aid this the page of address space for mapping APEI bufferswhile in_nmi() is always reserved, and ghes_ioremap_pfn_nmi() ischanged to use the helper methods to find the prot_t to map with inthe same way as ghes_ioremap_pfn_irq().Signed-off-by: Tyler Baicar &lt;tbaicar@codeaurora.org&gt;CC: Jonathan (Zhixiong) Zhang &lt;zjzhang@codeaurora.org&gt;Reviewed-by: James Morse &lt;james.morse@arm.com&gt;Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt;Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Wed, 21 Jun 2017 18:17:09 +0000</pubDate>
        <dc:creator>Tyler Baicar &lt;tbaicar@codeaurora.org&gt;</dc:creator>
    </item>
<item>
        <title>44a69f61 - acpi, apei, ghes: Make NMI error notification to be GHES architecture extension.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#44a69f61</link>
        <description>acpi, apei, ghes: Make NMI error notification to be GHES architecture extension.Currently APEI depends on x86 architecture. It is because of NMI hardwareerror notification of GHES which is currently supported by x86 only.However, many other APEI features can be still used perfectly by otherarchitectures.This commit adds two symbols:1. HAVE_ACPI_APEI for those archs which support APEI.2. HAVE_ACPI_APEI_NMI which is used for NMI code isolation in ghes.c   file. NMI related data and functions are grouped so they can be wrapped   inside one #ifdef section. Appropriate function stubs are provided for   !NMI case.Note there is no functional changes for x86 due to hard selectedHAVE_ACPI_APEI and HAVE_ACPI_APEI_NMI symbols.Signed-off-by: Tomasz Nowicki &lt;tomasz.nowicki@linaro.org&gt;Acked-by: Borislav Petkov &lt;bp@suse.de&gt;Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Tue, 22 Jul 2014 09:20:12 +0000</pubDate>
        <dc:creator>Tomasz Nowicki &lt;tomasz.nowicki@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>51572753 - ACPI / APEI: Remove X86 redundant dependency for APEI GHES.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#51572753</link>
        <description>ACPI / APEI: Remove X86 redundant dependency for APEI GHES.ACPI_APEI already depends on X86, so there is no need to definesuch dependency for ACPI_APEI_GHES (Generic Hardware Error Source)again.Signed-off-by: Tomasz Nowicki &lt;tomasz.nowicki@linaro.org&gt;Acked-by: Borislav Petkov &lt;bp@suse.de&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Mon, 10 Feb 2014 16:23:36 +0000</pubDate>
        <dc:creator>Tomasz Nowicki &lt;tomasz.nowicki@linaro.org&gt;</dc:creator>
    </item>
<item>
        <title>fce7d3bf - x86/efi: Don&apos;t select EFI from certain special ACPI drivers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#fce7d3bf</link>
        <description>x86/efi: Don&apos;t select EFI from certain special ACPI driversCommit 7ea6c6c1 (&quot;Move cper.c from drivers/acpi/apei todrivers/firmware/efi&quot;) results in CONFIG_EFI being enabled evenwhen the user doesn&apos;t want this. Since ACPI APEI used to buildfine without UEFI (and as far as I know also has no functionaldepency on it), at least in that case using a reverse dependencyis wrong (and a straight one isn&apos;t needed).Whether the same is true for ACPI_EXTLOG I don&apos;t know - if thereis a functional dependency, it should depend on EFI rather thanselecting it. It certainly has (currently) no build dependency.Adjust Kconfig and build logic so that the bad dependency getsavoided.Signed-off-by: Jan Beulich &lt;jbeulich@suse.com&gt;Acked-by: Tony Luck &lt;tony.luck@intel.com&gt;Cc: Matt Fleming &lt;matt.fleming@intel.com&gt;Link: http://lkml.kernel.org/r/52AF1EBC020000780010DBF9@nat28.tlf.novell.comSigned-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Mon, 16 Dec 2013 14:39:40 +0000</pubDate>
        <dc:creator>Jan Beulich &lt;JBeulich@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>7ea6c6c1 - Move cper.c from drivers/acpi/apei to drivers/firmware/efi</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#7ea6c6c1</link>
        <description>Move cper.c from drivers/acpi/apei to drivers/firmware/eficper.c contains code to decode and print &quot;Common Platform Error Records&quot;.Originally added under drivers/acpi/apei because the only user was in thatsame directory - but now we have another consumer, and we shouldn&apos;t haveto force CONFIG_ACPI_APEI get access to this code.Since CPER is defined in the UEFI specification - the logical home forthis code is under drivers/firmware/efi/Acked-by: Matt Fleming &lt;matt.fleming@intel.com&gt;Acked-by: Ingo Molnar &lt;mingo@kernel.org&gt;Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Mon, 28 Oct 2013 21:06:55 +0000</pubDate>
        <dc:creator>Luck, Tony &lt;tony.luck@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>1230db8e - llist: Make some llist functions inline</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#1230db8e</link>
        <description>llist: Make some llist functions inlineBecause llist code will be used in performance critical schedulercode path, make llist_add() and llist_del_all() inline to avoidfunction calling overhead and related &apos;glue&apos; overhead.Signed-off-by: Huang Ying &lt;ying.huang@intel.com&gt;Acked-by: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;Signed-off-by: Peter Zijlstra &lt;a.p.zijlstra@chello.nl&gt;Link: http://lkml.kernel.org/r/1315461646-1379-2-git-send-email-ying.huang@intel.comSigned-off-by: Ingo Molnar &lt;mingo@elte.hu&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Thu, 08 Sep 2011 06:00:42 +0000</pubDate>
        <dc:creator>Huang Ying &lt;ying.huang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>03ba176a - ACPI APEI: Add Kconfig option IRQ_WORK for GHES</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#03ba176a</link>
        <description>ACPI APEI: Add Kconfig option IRQ_WORK for GHESIRQ_WORK is used by GHES, but it is selected by PERF_EVENT.For now PERF_EVENT is selected by x86 by default, butin concept, IRQ_WORK should be selected by GHES, not by others.Signed-off-by: Chen Gong &lt;gong.chen@linux.intel.com&gt;Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Wed, 10 Aug 2011 02:46:22 +0000</pubDate>
        <dc:creator>Chen Gong &lt;gong.chen@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>ba61ca4a - ACPI, APEI, GHES: Add hardware memory error recovery support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#ba61ca4a</link>
        <description>ACPI, APEI, GHES: Add hardware memory error recovery supportmemory_failure_queue() is called when recoverable memory errors arenotified by firmware to do the recovery work.Signed-off-by: Huang Ying &lt;ying.huang@intel.com&gt;Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Wed, 13 Jul 2011 05:14:28 +0000</pubDate>
        <dc:creator>Huang Ying &lt;ying.huang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>67eb2e99 - ACPI, APEI, GHES, printk support for recoverable error via NMI</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#67eb2e99</link>
        <description>ACPI, APEI, GHES, printk support for recoverable error via NMISome APEI GHES recoverable errors are reported via NMI, but printk isnot safe in NMI context.To solve the issue, a lock-less memory allocator is used to allocatememory in NMI handler, save the error record into the allocatedmemory, put the error record into a lock-less list.  On the otherhand, an irq_work is used to delay the operation from NMI context toIRQ context.  The irq_work IRQ handler will remove nodes fromlock-less list, printk the error record and do some further processinginclude recovery operation, then free the memory.Signed-off-by: Huang Ying &lt;ying.huang@intel.com&gt;Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Wed, 13 Jul 2011 05:14:25 +0000</pubDate>
        <dc:creator>Huang Ying &lt;ying.huang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>86cd4733 - ACPI, APEI, GHES, Prevent GHES to be built as module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#86cd4733</link>
        <description>ACPI, APEI, GHES, Prevent GHES to be built as moduleGHES (Generic Hardware Error Source) is used to process hardware errornotification in firmware first mode.  But because firmware first modecan be turned on but can not be turned off, it is unreasonable tounload the GHES module with firmware first mode turned on.  To avoidconfusion, this patch makes GHES can be enabled/disabled inconfiguration time, but not built as module and unloaded at run time.Signed-off-by: Huang Ying &lt;ying.huang@intel.com&gt;Reviewed-by: Andi Kleen &lt;ak@linux.intel.com&gt;Reviewed-by: Matthew Garrett &lt;mjg@redhat.com&gt;Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Wed, 13 Jul 2011 05:14:18 +0000</pubDate>
        <dc:creator>Huang Ying &lt;ying.huang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>5d2a8342 - pstore: Fix Kconfig dependencies for apei-&gt;pstore</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#5d2a8342</link>
        <description>pstore: Fix Kconfig dependencies for apei-&gt;pstoreGeert Uytterhoeven ran a dependency checker which kicked out this warning:+ warning: (ACPI_APEI) selects PSTORE which has unmet direct dependencies (MISC_FILESYSTEMS):  =&gt; N/ARandy confirmed that the fix was to &quot;select MISC_FILESYSTEMS&quot; too.Tested-by: Randy Dunlap &lt;randy.dunlap@oracle.com&gt;Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Wed, 13 Apr 2011 17:48:12 +0000</pubDate>
        <dc:creator>Luck, Tony &lt;tony.luck@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>c413d768 - ACPI, APEI, Add PCIe AER error information printing support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#c413d768</link>
        <description>ACPI, APEI, Add PCIe AER error information printing supportThe AER error information printing support is implemented indrivers/pci/pcie/aer/aer_print.c.  So some string constants, functionsand macros definitions can be re-used without being exported.The original PCIe AER error information printing function is notre-used directly because the overall format is quite different.  Andchanging the original printing format may make some original users&apos;scripts broken.Signed-off-by: Huang Ying &lt;ying.huang@intel.com&gt;CC: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;CC: Zhang Yanmin &lt;yanmin.zhang@intel.com&gt;Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Mon, 21 Feb 2011 05:54:43 +0000</pubDate>
        <dc:creator>Huang Ying &lt;ying.huang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>0bb77c46 - pstore: X86 platform interface using ACPI/APEI/ERST</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#0bb77c46</link>
        <description>pstore: X86 platform interface using ACPI/APEI/ERSTThe &apos;error record serialization table&apos; in ACPI provides a suitableamount of persistent storage for use by the pstore filesystem.Signed-off-by: Tony Luck &lt;tony.luck@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Mon, 03 Jan 2011 22:22:11 +0000</pubDate>
        <dc:creator>Tony Luck &lt;tony.luck@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>58f87ed0 - ACPI: Fix typos</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#58f87ed0</link>
        <description>ACPI: Fix typosSigned-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Tue, 07 Sep 2010 16:49:45 +0000</pubDate>
        <dc:creator>Lucas De Marchi &lt;lucas.de.marchi@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>2ff729d5 - ACPI, APEI, ERST debug support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#2ff729d5</link>
        <description>ACPI, APEI, ERST debug supportThis patch adds debugging/testing support to ERST. A misc device isimplemented to export raw ERST read/write/clear etc operations to userspace. With this patch, we can add ERST testing support tolinuxfirmwarekit ISO (linuxfirmwarekit.org) to verify the kernelsupport and the firmware implementation.Signed-off-by: Huang Ying &lt;ying.huang@intel.com&gt;Acked-by: Randy Dunlap &lt;randy.dunlap@oracle.com&gt;Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Thu, 12 Aug 2010 03:55:17 +0000</pubDate>
        <dc:creator>Huang Ying &lt;ying.huang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>d334a491 - ACPI, APEI, Generic Hardware Error Source memory error support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#d334a491</link>
        <description>ACPI, APEI, Generic Hardware Error Source memory error supportGeneric Hardware Error Source provides a way to report platformhardware errors (such as that from chipset). It works in so called&quot;Firmware First&quot; mode, that is, hardware errors are reported tofirmware firstly, then reported to Linux by firmware. This way, somenon-standard hardware error registers or non-standard hardware linkcan be checked by firmware to produce more valuable hardware errorinformation for Linux.Now, only SCI notification type and memory errors are supported. Morenotification type and hardware error type will be added later. Thesememory errors are reported to user space through /dev/mcelog viafaking a corrected Machine Check, so that the error memory page can beofflined by /sbin/mcelog if the error count for one page is beyond thethreshold.On some machines, Machine Check can not report physical address forsome corrected memory errors, but GHES can do that. So this simplifiedGHES is implemented firstly.Signed-off-by: Huang Ying &lt;ying.huang@intel.com&gt;Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Tue, 18 May 2010 06:35:20 +0000</pubDate>
        <dc:creator>Huang Ying &lt;ying.huang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>e4021345 - ACPI, APEI, EINJ support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/acpi/apei/Kconfig#e4021345</link>
        <description>ACPI, APEI, EINJ supportEINJ provides a hardware error injection mechanism, this is useful fordebugging and testing of other APEI and RAS features.Signed-off-by: Huang Ying &lt;ying.huang@intel.com&gt;Signed-off-by: Andi Kleen &lt;ak@linux.intel.com&gt;Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;

            List of files:
            /linux-6.15/drivers/acpi/apei/Kconfig</description>
        <pubDate>Tue, 18 May 2010 06:35:14 +0000</pubDate>
        <dc:creator>Huang Ying &lt;ying.huang@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
