Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp8272ybl; Wed, 21 Aug 2019 13:53:42 -0700 (PDT) X-Google-Smtp-Source: APXvYqyztikJFNT+sJtr4yJq5AWRZ6cl9F07PZ9V9Qytq916TCpYMchFppAnVn991Whb5LQxDDnZ X-Received: by 2002:a17:902:8f90:: with SMTP id z16mr35689149plo.138.1566420822647; Wed, 21 Aug 2019 13:53:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566420822; cv=none; d=google.com; s=arc-20160816; b=mmIv1IQInxpEC/ccI8qmnEdiayPBloZFZZrj1k88iWv248rbTCL0uqOygm7+JIqG7L atGnzM1n/3Y8OFHhvenyCnLR/uksk7I9Na7FwBzY9jxUG8bQRCwRoKemt7S3vMiGjGg/ E5BcT+qq7W+F2GX83Qd/AAR+Sv5C0GXg5PCWvFbsSaApnD8Q/z7490tfiv0+7wRunejs ZoDQSO3MqJI9u3o2jv6uR17En9/gEIc9SxcxXSIfAbtVLzkYm8MoNdDXPNFprHq7O8ti eB0SGuVIXlFSLyOORJvwDlkBOvPOHunS0+3IPaI6USR6YE5ZHAQrPhLw4mu8m3GkpNNF plPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=ce27Cd54EABjspfyO4CpSrYijPsAem+R5BZqRQLuMqM=; b=r9L3xOc8flho3KAzkxeIZoMGg+KDXd1vKSObXoLRUofo6h946yFud78BRL+oypokDb 8Eu2RWdTKmMUNYb0yk3Wnj8ocveWpOiBeeGokrE/mdtlEwrhecxMjEZsBkbu/A035Co+ Bj9rWcG0cEhcZ6rjR2fGQXj8f+PwUpexRlszsCMTREJ36w9Ssqnn79LnuUweIjEiEgg0 V09NUpeYuqjFO2XSeZI7F1RzWngmkTqw/yVCVsUBJq620jbvwyPwiR0mPjSIia8bCjkK H3mO0N+hBNF8TsivxLExsm+gSjhWTs92jUk/Gpyjy5srWC9mtjoFZknTn2lUxjlIEoWa W9iQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y184si16679080pfb.162.2019.08.21.13.53.27; Wed, 21 Aug 2019 13:53:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729740AbfHURXD (ORCPT + 99 others); Wed, 21 Aug 2019 13:23:03 -0400 Received: from foss.arm.com ([217.140.110.172]:33878 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727037AbfHURXC (ORCPT ); Wed, 21 Aug 2019 13:23:02 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5040D344; Wed, 21 Aug 2019 10:23:02 -0700 (PDT) Received: from [10.1.196.105] (eglon.cambridge.arm.com [10.1.196.105]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id CC56F3F718; Wed, 21 Aug 2019 10:23:00 -0700 (PDT) Subject: Re: [PATCH RFC 2/4] ACPI: APEI: Add ghes_handle_memory_failure to the new notification method To: Shiju Jose Cc: linux-acpi@vger.kernel.org, linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org, rjw@rjwysocki.net, lenb@kernel.org, tony.luck@intel.com, bp@alien8.de, baicar@os.amperecomputing.com, linuxarm@huawei.com, jonathan.cameron@huawei.com, tanxiaofei@huawei.com References: <20190812101149.26036-1-shiju.jose@huawei.com> <20190812101149.26036-3-shiju.jose@huawei.com> From: James Morse Message-ID: <12b3ccff-0cda-0467-a9ba-0682be6f333e@arm.com> Date: Wed, 21 Aug 2019 18:22:59 +0100 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2 MIME-Version: 1.0 In-Reply-To: <20190812101149.26036-3-shiju.jose@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 12/08/2019 11:11, Shiju Jose wrote: > This patch adds ghes_handle_memory_failure to the new error > notification method. The commit message doesn't answer the question: why? The existing code works. This just looks like additional churn. Given a user, I think the vendor specific example is useful. I don't think making this thing more pluggable is a good idea. Thanks, James