From: Zhou Wang <wangzhou1@hisilicon.com>
To: Wei Xu <xuwei5@hisilicon.com>, <xuwei5@huawei.com>
Cc: linuxarm@huawei.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: defconfig: Enable CONFIG_ACPI_APEI_PCIEAER
Date: Fri, 16 Aug 2019 10:53:52 +0800 [thread overview]
Message-ID: <5D561AC0.5000401@hisilicon.com> (raw)
In-Reply-To: <5D561543.3040505@hisilicon.com>
On 2019/8/16 10:30, Wei Xu wrote:
> Hi Zhou,
>
> On 2019/7/29 9:32, Zhou Wang wrote:
>> HiSilicon D06 board needs this config to support PCIe AER error report.
>>
>> Signed-off-by: Zhou Wang <wangzhou1@hisilicon.com>
>
> Thanks!
> Patch applied and the commit message changed as follows:
>
> Enable the ACPI_APEI_PCIEAER configuration to support PCIe AER error report
> for the Hisilicon D06 board and the dependencies PCIEAER and ACPI_APEI have
> been enabled in the default config.
Thanks and Best,
Zhou
>
> Best Regards,
> Wei
>
>> ---
>> arch/arm64/configs/defconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
>> index 74f0a19..8167d6f 100644
>> --- a/arch/arm64/configs/defconfig
>> +++ b/arch/arm64/configs/defconfig
>> @@ -119,6 +119,7 @@ CONFIG_IMX_SCU_PD=y
>> CONFIG_ACPI=y
>> CONFIG_ACPI_APEI=y
>> CONFIG_ACPI_APEI_GHES=y
>> +CONFIG_ACPI_APEI_PCIEAER=y
>> CONFIG_ACPI_APEI_MEMORY_FAILURE=y
>> CONFIG_ACPI_APEI_EINJ=y
>> CONFIG_VIRTUALIZATION=y
>
>
>
> .
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-08-16 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 1:32 [PATCH] arm64: defconfig: Enable CONFIG_ACPI_APEI_PCIEAER Zhou Wang
2019-08-16 2:30 ` Wei Xu
2019-08-16 2:53 ` Zhou Wang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5D561AC0.5000401@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=xuwei5@hisilicon.com \
--cc=xuwei5@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.