From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753718AbaIOHeT (ORCPT ); Mon, 15 Sep 2014 03:34:19 -0400 Received: from mail-pd0-f177.google.com ([209.85.192.177]:54675 "EHLO mail-pd0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753686AbaIOHeN (ORCPT ); Mon, 15 Sep 2014 03:34:13 -0400 Date: Sun, 14 Sep 2014 23:40:10 -0700 From: Olof Johansson To: Hanjun Guo Cc: Catalin Marinas , "Rafael J. Wysocki" , Mark Rutland , Grant Likely , Will Deacon , Graeme Gregory , Arnd Bergmann , Sudeep Holla , Jon Masters , Jason Cooper , Marc Zyngier , Bjorn Helgaas , Daniel Lezcano , Mark Brown , Rob Herring , Robert Richter , Lv Zheng , Robert Moore , Lorenzo Pieralisi , Liviu Dudau , Randy Dunlap , Charles.Garcia-Tobin@arm.com, linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linaro-acpi@lists.linaro.org, Tomasz Nowicki Subject: Re: [PATCH v4 10/18] ACPI / table: Print GIC information when MADT is parsed Message-ID: <20140915064010.GD26649@localhost> References: <1410530416-30200-1-git-send-email-hanjun.guo@linaro.org> <1410530416-30200-11-git-send-email-hanjun.guo@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1410530416-30200-11-git-send-email-hanjun.guo@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Sep 12, 2014 at 10:00:08PM +0800, Hanjun Guo wrote: > When MADT is parsed, print GIC information to make the boot > log look pretty. If you do this for prettiness, having an example output in the commit message would be a nice touch. The question is why it's needed though? Do we really need all this verbose information in dmesg when it could be found out in other ways instead? x86 is notoriously verbose in some of these aspects, I'm not sure it's something we need to mimic here? -Olof