From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754754AbaIVUb6 (ORCPT ); Mon, 22 Sep 2014 16:31:58 -0400 Received: from cavan.codon.org.uk ([93.93.128.6]:41360 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752887AbaIVUb4 (ORCPT ); Mon, 22 Sep 2014 16:31:56 -0400 Date: Mon, 22 Sep 2014 21:31:36 +0100 From: Matthew Garrett To: Pavel Machek Cc: 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 , "Rafael J. Wysocki" , linux-kernel@vger.kernel.org, Sudeep Holla , Olof Johansson Subject: Re: [PATCH v4 18/18] Documentation: ACPI for ARM64 Message-ID: <20140922203136.GA32156@srcf.ucam.org> References: <1410530416-30200-1-git-send-email-hanjun.guo@linaro.org> <1410530416-30200-19-git-send-email-hanjun.guo@linaro.org> <20140922194841.GA9868@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140922194841.GA9868@amd> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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) -- Matthew Garrett | mjg59@srcf.ucam.org