Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751900AbdH2XGr (ORCPT ); Tue, 29 Aug 2017 19:06:47 -0400 Received: from mga03.intel.com ([134.134.136.65]:18962 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751378AbdH2XGo (ORCPT ); Tue, 29 Aug 2017 19:06:44 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,446,1498546800"; d="scan'208";a="146039453" From: "Luck, Tony" To: Borislav Petkov , "Baicar, Tyler" CC: "rjw@rjwysocki.net" , "lenb@kernel.org" , "will.deacon@arm.com" , "james.morse@arm.com" , "prarit@redhat.com" , "punit.agrawal@arm.com" , "shiju.jose@huawei.com" , "andriy.shevchenko@linux.intel.com" , "linux-acpi@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: RE: [PATCH] acpi: apei: call into AER handling regardless of severity Thread-Topic: [PATCH] acpi: apei: call into AER handling regardless of severity Thread-Index: AQHTIRTwxlzMfht6FkaxU1Od08Dfg6Kb9D7g Date: Tue, 29 Aug 2017 23:06:43 +0000 Message-ID: <3908561D78D1C84285E8C5FCA982C28F61360FE6@ORSMSX114.amr.corp.intel.com> References: <1503940314-29526-1-git-send-email-tbaicar@codeaurora.org> <20170829082055.u3qpwtgyzxjxfvup@pd.tnic> <9abb2e99-44be-3315-47d9-2689b6c76d79@codeaurora.org> <20170829221932.ojkvr4y6s76hcpkj@pd.tnic> In-Reply-To: <20170829221932.ojkvr4y6s76hcpkj@pd.tnic> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.22.254.140] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v7TN6nHF022777 Content-Length: 258 Lines: 10 > So let's find out first why do we have to look at both severities. > > Tony, any ideas? Sorry, no ideas. I haven't tried to dig through this mess to take action ... just skimmed through the code a while back when we were just logging the errors. -Tony