From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756381AbaIQTXY (ORCPT ); Wed, 17 Sep 2014 15:23:24 -0400 Received: from cavan.codon.org.uk ([93.93.128.6]:52553 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755785AbaIQTXV (ORCPT ); Wed, 17 Sep 2014 15:23:21 -0400 Date: Wed, 17 Sep 2014 20:22:59 +0100 From: Matthew Garrett To: "Rafael J. Wysocki" Cc: Hanjun Guo , Catalin Marinas , Mark Rutland , Olof Johansson , Grant Likely , Will Deacon , linaro-acpi@lists.linaro.org, Liviu Dudau , Lv Zheng , Rob Herring , Lorenzo Pieralisi , Daniel Lezcano , Robert Moore , linux-acpi@vger.kernel.org, Charles.Garcia-Tobin@arm.com, Robert Richter , Jason Cooper , Arnd Bergmann , Marc Zyngier , Jon Masters , Mark Brown , Bjorn Helgaas , linux-arm-kernel@lists.infradead.org, Graeme Gregory , Randy Dunlap , linux-kernel@vger.kernel.org, Sudeep Holla , Darren Hart Subject: Re: [PATCH v4 18/18] Documentation: ACPI for ARM64 Message-ID: <20140917192259.GA18980@srcf.ucam.org> References: <1410530416-30200-1-git-send-email-hanjun.guo@linaro.org> <1410530416-30200-19-git-send-email-hanjun.guo@linaro.org> <20140917014410.GC31214@srcf.ucam.org> <4416582.iOjLNrLDZE@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4416582.iOjLNrLDZE@vostro.rjw.lan> 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 Wed, Sep 17, 2014 at 09:37:42PM +0200, Rafael J. Wysocki wrote: > There are no implied IP issues with using the information there I know of and > if there's any fine print anywhere that may suggest so, please let me know. Using the information should be fine, but my understanding of the UEFI forum rules is that any submissions to UEFI specs must be from UEFI forum members - there are concerns around accidentally including patented material. The easy way around this is just for the bindings to be managed outside UEFI. -- Matthew Garrett | mjg59@srcf.ucam.org