From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH v4 18/18] Documentation: ACPI for ARM64 Date: Tue, 23 Sep 2014 00:46:24 +0200 Message-ID: <2486199.jzqMgLksH8@vostro.rjw.lan> References: <1410530416-30200-1-git-send-email-hanjun.guo@linaro.org> <20140922194841.GA9868@amd> <20140922203136.GA32156@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7Bit Return-path: Received: from v094114.home.net.pl ([79.96.170.134]:59999 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754863AbaIVW0i (ORCPT ); Mon, 22 Sep 2014 18:26:38 -0400 In-Reply-To: <20140922203136.GA32156@srcf.ucam.org> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Matthew Garrett Cc: Pavel Machek , Hanjun Guo , Mark Rutland , linaro-acpi@lists.linaro.org, Catalin Marinas , Will Deacon , Lv Zheng , Rob Herring , Lorenzo Pieralisi , Daniel Lezcano , Robert Moore , linux-acpi@vger.kernel.org, Jon Masters , Grant Likely , Charles.Garcia-Tobin@arm.com, Robert Richter , Jason Cooper , Arnd Bergmann , Marc Zyngier , Liviu Dudau , Mark Brown , Bjorn Helgaas , linux-arm-kernel@lists.infradead.org, Graeme Gregory , Randy Dunlap On Monday, September 22, 2014 09:31:36 PM Matthew Garrett wrote: > On Mon, Sep 22, 2014 at 09:48:41PM +0200, Pavel Machek wrote: > > On Fri 2014-09-12 22:00:16, Hanjun Guo wrote: > > > +No code shall be accepted into the kernel unless it complies with the released > > > +standards from UEFI ASWG. If there are features missing from ACPI to make it > > > +function on a platform, ECRs should be submitted to ASWG and go through the > > > +approval process. > > > > Surely this should be narrowed down somehow? Or is reading all the > > released standards from ASWG mandatory before patching the kernel now? > > > > Spelling out wtf ECR is would be nice, too. > > Explicit Change Request. These can only be filed by paid-up members of > the UEFI Forum, so I suspect this requirement is going to be unworkable > (there's plenty of ACPI support code for large x86 vendors which isn't > part of any ACPI spec). Why do you think so? Linux Foundation can do that on behalf of the community if no one else. -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center.