Received: by 10.192.165.148 with SMTP id m20csp5039910imm; Tue, 24 Apr 2018 12:36:51 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+o1fju/FA0oTrUHX6ZNASixxx+EdNB2JoMxckWMRHOKshS3N+OOZhgbYqfUGp/dBmx/EL9 X-Received: by 10.99.158.85 with SMTP id r21mr21317889pgo.312.1524598611359; Tue, 24 Apr 2018 12:36:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524598611; cv=none; d=google.com; s=arc-20160816; b=Jtvn1/PStImuFghQ5rf94s3vLYzgqCwrAu4FOIpYWg2oZYLBHAjxdL2TscQqzPAy91 cIvuHTlGalau6yffd61zWkDoeAX/giFcD8T+qt1JcPScWcYc+GDH1riq18kHB+1n5Egi Wxvfz83EW/0XcGKGEPOjaCu8VmwgeEiryzpmKXie0bnT5hn0cnw4Aua4kCIJxkL1LJji PYNgJGRwzjvvVNG3RPHTWJ+YqZA1pMYHJNNHsTNS7LA6lWJQMXjOrH8xALeaMWbhekOM QEZPqN2au4Myk8GpRkOmR1fXCmIULJt8r2AmPNE+8WuqSxOZ/AHugSM5hoSV4CYcr+ZE bTHQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from :arc-authentication-results; bh=yMhRCtn0KGTaf9EjYuFbh7tjSxqDiw/E9aEKPsfAhXc=; b=gl/FUh6ff9Kopv7kC3eYcIZWGUU6JgvrXk4Qx4zdqqIfDsFQLUSBZD4hazc1/Czghz VU4qMFRSc6d1Y1r3TkNYp+rPsciQ+GEEeoYZs3hcRlWfUIg+4VbhzIJ+fWw42imW/TN4 jtp0/sQGHqxWVKELYDOsU7u/O6zoe/hsN/E7qee2rseIbuUnwhypCuREf0KD+aTLhXiW ebyAv5+EMgpEj8rb313vdLAr38X6AkN1sGKMeoIcA6u47VJiPR536ta2rm/x9Udghm8/ u92E98cjKu5Mo+AceA8aNuaT8OIOnJw2CzxEgeI7QsMfZSNkqpgbNgBX0eeV3CIHy6t+ UPAA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1-v6si10050858plj.122.2018.04.24.12.36.37; Tue, 24 Apr 2018 12:36:51 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752531AbeDXTfR (ORCPT + 99 others); Tue, 24 Apr 2018 15:35:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:34006 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751110AbeDXTfO (ORCPT ); Tue, 24 Apr 2018 15:35:14 -0400 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id CB50D4903F; Tue, 24 Apr 2018 19:35:14 +0000 (UTC) Received: from fidelio.ahs3.com (ovpn-117-94.phx2.redhat.com [10.3.117.94]) by smtp.corp.redhat.com (Postfix) with ESMTP id 0EDA783B2A; Tue, 24 Apr 2018 19:35:11 +0000 (UTC) From: Al Stone To: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Al Stone Subject: [PATCH v2 0/3] mailbox: ACPI: Remove incorrect error message about parsing PCCT Date: Tue, 24 Apr 2018 13:35:02 -0600 Message-Id: <20180424193505.6934-1-ahs3@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Tue, 24 Apr 2018 19:35:14 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This set of patches provide some cleanup in ACPI for minor issues found while correcting a bogus error message (the first two patches), and the correction for the error message itself (patch 3/3). Note that patches 1/3 and 2/3 are not required for 3/3 to work: 1/3 only changes a comment and 2/3 makes an ACPI table parsing loop a wee bit more robust. For patch 3/3, many systems on boot have been reporting "Error parsing PCC subspaces from PCCT" which turns out to not be an error at all. The issue is that the probe for ACPI mailboxes defined in the PCCT (Platform Communications Channel Table) makes a faulty assumption about the content of the PCCT. What's more, when the error is reported, no further PCC mailboxes are set up, even when they have been defined in the PCCT. So, in the reported cases, there was no error and the data in the PCCT was being ignored. This is described in more detail in patch 3/3. Since these patches primarily involve ACPI usages, it may make sense for all of them to go through the linux-acpi tree; clearly, this is up to the maintainers, though. v2: -- removed one extraneous '+' in a comment in patch 3/3 -- fixed an if test that had a predicate that kbuild pointed out would always be zero Al Stone (3): ACPI: improve function documentation for acpi_parse_entries_array() ACPI: ensure acpi_parse_entries_array() does not access non-existent table data mailbox: ACPI: erroneous error message when parsing the ACPI PCCT drivers/acpi/tables.c | 9 ++--- drivers/mailbox/pcc.c | 99 +++++++++++++++++++++++++++++++++++++-------------- 2 files changed, 78 insertions(+), 30 deletions(-) -- 2.14.3