Received: by 10.213.65.68 with SMTP id h4csp155415imn; Tue, 3 Apr 2018 17:44:51 -0700 (PDT) X-Google-Smtp-Source: AIpwx48zH5SsJUPkfA4xRvo4aGEe2ApoQe830Ansq5sXlqs0raGKwi3C3N7pSTe57Um/u8GUNeR0 X-Received: by 2002:a17:902:a589:: with SMTP id az9-v6mr16184041plb.283.1522802691287; Tue, 03 Apr 2018 17:44:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522802691; cv=none; d=google.com; s=arc-20160816; b=PLrZEK3qOK+Lsyucg8NxokRa+ccvr9Ovk9THV2/eLyl1Je7VHUCMpldsbSEZd9iNgg 3j/2zR7x4B0RwzPkx60lvJ2JZYzKsqA6ai3GgrMbVPnlCCfb1ez5zqK/d+Mr8Ch6cAg3 pc7REHgLcnzoNa0JMGQnyVXu5u5N09I0m2FAyJ0e1YSe3wl1H9nN7A1MmgjKq5YyscID SOhjbWXO1fjc+ZQyH9we0wo9Mh7XzlJlRQEuLP6ulgRDLMCLHf0QPdsI3YJhgIO9vdaX Ol6/prt+9LeorKc++kDHkwpHcXgblh76PE833cFuKzDcxb25jVfLSQqW1+TzswImDxGu DSFg== 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=dhA4sSNk2IOgofq2zbNnX527ga5pnXiPdnBPflPSI50=; b=a5qwSQLvH6+5BKvTnNWWCOJY0a0KAqzMxUjI904p3Mw3CaXubPUCpYrZD4ilt0SY+c xTtGVrvYEStPX4z4CNDx/+ZSH++5G46BUASnRa5AEa6f1KCqUmOcwkP/gRyYppcTLxXs 4bcX9dglbFPjZOwfxj4j2drILrg03vpsn3EwZ0CCT9hv4+YuiUBzAfWPFjzPw8xcasNo Y9a3TkbS0T/qo2qqTPkk4CnIH9RTzrCnXAYrLgv7Q9/usItHKrCDeZGsqHzFZkadsZww oV++PWkN9sOjifEABAHm5hCJ0KqD5/+byerVh1QOQm5qL87CwAbTj9KzGZRmn2jEVYTz XDSA== 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 s9-v6si1753349plr.493.2018.04.03.17.44.37; Tue, 03 Apr 2018 17:44: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 S1754233AbeDDAmb (ORCPT + 99 others); Tue, 3 Apr 2018 20:42:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:29220 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754156AbeDDAmW (ORCPT ); Tue, 3 Apr 2018 20:42:22 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 8D60F7FEA2; Wed, 4 Apr 2018 00:42:22 +0000 (UTC) Received: from fidelio.ahs3.com (ovpn-116-126.phx2.redhat.com [10.3.116.126]) by smtp.corp.redhat.com (Postfix) with ESMTP id 96447822EE; Wed, 4 Apr 2018 00:42:17 +0000 (UTC) From: Al Stone To: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Al Stone Subject: [PATCH 0/3] mailbox: ACPI: Remove incorrect error message about parsing PCCT Date: Tue, 3 Apr 2018 18:42:08 -0600 Message-Id: <20180404004211.6141-1-ahs3@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Wed, 04 Apr 2018 00:42:22 +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. 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