From: Borislav Petkov <bp@suse.de>
To: Dongjiu Geng <gengdongjiu@huawei.com>
Cc: tbaicar@codeaurora.org, james.morse@arm.com, will.deacon@arm.com,
rjw@rjwysocki.net, lenb@kernel.org, robert.moore@intel.com,
lv.zheng@intel.com, mark.rutland@arm.com,
kristina.martsenko@arm.com, mingo@kernel.org,
punit.agrawal@arm.com, stephen.boyd@linaro.org,
kamensky@cisco.com, prarit@redhat.com, shiju.jose@huawei.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
devel@acpica.or
Subject: Re: [PATCH v5 1/2] acpi: apei: remove the unused dead-code for SEA/NMI notification type
Date: Tue, 17 Oct 2017 18:43:36 +0200 [thread overview]
Message-ID: <20171017164336.cedso3f35lpeam7f@pd.tnic> (raw)
In-Reply-To: <1508227341-15651-1-git-send-email-gengdongjiu@huawei.com>
On Tue, Oct 17, 2017 at 04:02:20PM +0800, Dongjiu Geng wrote:
> @@ -1061,23 +1052,9 @@ static void ghes_nmi_init_cxt(void)
> init_irq_work(&ghes_proc_irq_work, ghes_proc_in_irq);
> }
> #else /* CONFIG_HAVE_ACPI_APEI_NMI */
> -static inline void ghes_nmi_add(struct ghes *ghes)
> -{
> - pr_err(GHES_PFX "ID: %d, trying to add NMI notification which is not supported!\n",
> - ghes->generic->header.source_id);
> - BUG();
> -}
> -
> -static inline void ghes_nmi_remove(struct ghes *ghes)
> -{
> - pr_err(GHES_PFX "ID: %d, trying to remove NMI notification which is not supported!\n",
> - ghes->generic->header.source_id);
> - BUG();
> -}
> -
So GHES NMI notification method is x86-only AFAIK and HAVE_ACPI_APEI_NMI
is selected only on x86. Why are you removing those guards? Does ARM
have ACPI_HEST_NOTIFY_NMI notification type now too?
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2017-10-17 16:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 8:02 Dongjiu Geng
2017-10-17 8:02 ` [PATCH v5 2/2] acpi: apei: Add SEI notification type support for ARMv8 Dongjiu Geng
2017-10-17 17:06 ` Borislav Petkov
2017-10-18 5:00 ` gengdongjiu
2017-10-18 9:06 ` Borislav Petkov
2017-10-18 9:17 ` gengdongjiu
2017-10-18 9:25 ` Borislav Petkov
2017-10-18 9:44 ` James Morse
2017-10-18 10:04 ` Borislav Petkov
2017-10-18 10:25 ` gengdongjiu
2017-10-18 10:21 ` gengdongjiu
2017-10-18 10:26 ` James Morse
2017-10-18 11:39 ` gengdongjiu
2017-10-17 14:06 ` [PATCH v5 1/2] acpi: apei: remove the unused dead-code for SEA/NMI notification type Tyler Baicar
2017-10-17 16:43 ` Borislav Petkov [this message]
2017-10-18 3:04 ` gengdongjiu
2017-10-18 10:17 ` Borislav Petkov
2017-10-18 12:27 ` gengdongjiu
2017-10-18 13:14 ` Borislav Petkov
2017-10-18 15:14 gengdongjiu
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=20171017164336.cedso3f35lpeam7f@pd.tnic \
--to=bp@suse.de \
--cc=devel@acpica.or \
--cc=gengdongjiu@huawei.com \
--cc=james.morse@arm.com \
--cc=kamensky@cisco.com \
--cc=kristina.martsenko@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=prarit@redhat.com \
--cc=punit.agrawal@arm.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=shiju.jose@huawei.com \
--cc=stephen.boyd@linaro.org \
--cc=tbaicar@codeaurora.org \
--cc=will.deacon@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®