From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932484AbbA2XSA (ORCPT ); Thu, 29 Jan 2015 18:18:00 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55742 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932434AbbA2XR5 (ORCPT ); Thu, 29 Jan 2015 18:17:57 -0500 Message-ID: <54CABF46.3050701@redhat.com> Date: Thu, 29 Jan 2015 18:16:22 -0500 From: Jon Masters Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Catalin Marinas CC: Timur Tabi , Ard Biesheuvel , Mark Rutland , Rob Herring , "phoenix.liyi@huawei.com" , Robert Richter , "linux-acpi@vger.kernel.org" , Arnd Bergmann , "linaro-acpi@lists.linaro.org" , Marc Zyngier , Will Deacon , Randy Dunlap , "Rafael J. Wysocki" , lkml , "grant.likely@linaro.org" , "wangyijing@huawei.com" , Mark Brown , "hanjun.guo@linaro.org" , Olof Johansson , Bjorn Helgaas , "linux-arm-kernel@lists.infradead.org" , Jason Cooper Subject: Re: [Linaro-acpi] [PATCH v7 04/17] ARM64 / ACPI: Introduce early_param for "acpi" and pass acpi=force to enable ACPI References: <20150128181453.GG31752@e104818-lin.cambridge.arm.com> <54C92804.5090806@codeaurora.org> <20150129151956.GF8951@e104818-lin.cambridge.arm.com> <54CA7A42.5080800@codeaurora.org> <54CA7D4A.5090709@codeaurora.org> <54CA7F94.6000305@redhat.com> <20150129231120.GA23786@e104818-lin.cambridge.arm.com> In-Reply-To: <20150129231120.GA23786@e104818-lin.cambridge.arm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/29/2015 06:11 PM, Catalin Marinas wrote: > Sorry Jon but statements like this make me wonder whether we should > simply let the whole ARM ACPI be an out of tree distro business. We > spend a long time discussing OS-agnostic firmware implementation, > planning mini-summits, just to get certain Linux distro representative > stating that the kernel-firmware interface we discuss here only matters > for those planning to follow upstream. Certain Linux distros will play > by other rules. Oh, don't take it that way - I just mean that if someone needs a different ACPI always on, they can do that separately. I support your position on upstream at this time! :) Jon.