From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756734AbaIQTvh (ORCPT ); Wed, 17 Sep 2014 15:51:37 -0400 Received: from v094114.home.net.pl ([79.96.170.134]:55011 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756231AbaIQTvg (ORCPT ); Wed, 17 Sep 2014 15:51:36 -0400 From: "Rafael J. Wysocki" To: Matthew Garrett 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 Date: Wed, 17 Sep 2014 22:11:13 +0200 Message-ID: <1628662.T2ReQ4irMm@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/3.16.0-rc5+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <20140917192259.GA18980@srcf.ucam.org> References: <1410530416-30200-1-git-send-email-hanjun.guo@linaro.org> <4416582.iOjLNrLDZE@vostro.rjw.lan> <20140917192259.GA18980@srcf.ucam.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday, September 17, 2014 08:22:59 PM Matthew Garrett wrote: > 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 documents in question are not regarded as UEFI specs, however. They are just hosted by UEFI. > The easy way around this is just for the bindings to > be managed outside UEFI. Again, there's a difference between UEFI material and the UEFI hosting something (but not maintaining it). In principle, the bindings could be hosted by UEFI, but maintained by community members. Rafael