From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S935119AbcKPVga (ORCPT <rfc822;w@1wt.eu>);
        Wed, 16 Nov 2016 16:36:30 -0500
Received: from mail.kernel.org ([198.145.29.136]:51266 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S932263AbcKPVg3 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 16 Nov 2016 16:36:29 -0500
Date: Wed, 16 Nov 2016 15:36:25 -0600
From: Bjorn Helgaas <helgaas@kernel.org>
To: Huang Ying <ying.huang@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Len Brown <lenb@kernel.org>,
        linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: GHES platform devices
Message-ID: <20161116213625.GA10368@bhelgaas-glaptop.roam.corp.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Huang,

7ad6e9435596 ("ACPI, APEI, Manage GHES as platform devices") added
platform devices so the GHES driver could be built as a module and
automatically loaded when needed.

Later, 86cd47334b00 ("ACPI, APEI, GHES, Prevent GHES to be built as
module") removed the ability to build GHES as a module.

Should we revert 7ad6e9435596?  It's inconsistent to handle GHES, but
not other error sources, as a platform device.  And having it as a
platform device probably puts gunk in sysfs that we don't need.

Bjorn