From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752131AbaHTD1g (ORCPT ); Tue, 19 Aug 2014 23:27:36 -0400 Received: from mail-pd0-f176.google.com ([209.85.192.176]:64922 "EHLO mail-pd0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751997AbaHTD1f (ORCPT ); Tue, 19 Aug 2014 23:27:35 -0400 Message-ID: <53F41543.4090602@linaro.org> Date: Wed, 20 Aug 2014 11:25:55 +0800 From: Hanjun Guo User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Geoff Levand CC: Catalin Marinas , "Rafael J. Wysocki" , Mark Rutland , linaro-acpi@lists.linaro.org, Liviu Dudau , Lv Zheng , Rob Herring , Lorenzo Pieralisi , Daniel Lezcano , Robert Moore , linux-acpi@vger.kernel.org, Grant Likely , Charles.Garcia-Tobin@arm.com, Robert Richter , Jason Cooper , Arnd Bergmann , Marc Zyngier , Will Deacon , Tomasz Nowicki , Mark Brown , Bjorn Helgaas , linux-arm-kernel@lists.infradead.org, Graeme Gregory , Randy Dunlap , linux-kernel@vger.kernel.org, Sudeep Holla , Olof Johansson Subject: Re: [PATCH v2 08/18] ARM64 / ACPI: Get the enable method for SMP initialization in ACPI way References: <1407166105-17675-1-git-send-email-hanjun.guo@linaro.org> <1407166105-17675-9-git-send-email-hanjun.guo@linaro.org> <1408388212.22761.100.camel@smoke> <53F33EDC.3090203@linaro.org> <1408476326.22761.134.camel@smoke> In-Reply-To: <1408476326.22761.134.camel@smoke> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2014-8-20 3:25, Geoff Levand wrote: > Hi Hanjun, > > On Tue, 2014-08-19 at 20:11 +0800, Hanjun Guo wrote: >> On 2014-8-19 2:56, Geoff Levand wrote: > >>> message = acpi_disabled ? dn->full_name : ""; >>> >>> ... >>> >>> pr_warn("CPU %d: %s unsupported enable-method property: %s\n", >>> cpu, message, enable_method) >> >> In ACPI, there is no enable-method property, it is a term from, so I think the >> message printed can be separated. > > I think it better to have a single message that can cover all > than to have separate messages. Wouldn't the enable method be > "acpi-parking" or "acpi-psci"? Then something like this would > work: > > pr_warn("CPU %d: %s Unsupported enable method: %s\n", cpu, message, enable_method); Thanks for the suggestion, I will update it in next version. Thanks Hanjun