From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Rutland Subject: Re: [PATCH v19 10/15] clocksource/drivers/arm_arch_timer: Refactor the timer init code to prepare for GTDT Date: Tue, 17 Jan 2017 12:29:21 +0000 Message-ID: <20170117122921.GE11939@leverpostej> References: <20161221064603.11830-1-fu.wei@linaro.org> <20161221064603.11830-11-fu.wei@linaro.org> <20170116183032.GL5908@leverpostej> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Timur Tabi Cc: Linaro ACPI Mailman List , Catalin Marinas , Will Deacon , rruigrok@codeaurora.org, Wim Van Sebroeck , Fu Wei , Wei Huang , Lorenzo Pieralisi , Al Stone , Tomasz Nowicki , Daniel Lezcano , ACPI Devel Maling List , Guenter Roeck , Len Brown , "Abdulhamid, Harb" , Julien Grall , linux-watchdog@vger.kernel.org, Arnd Bergmann , Marc Zyngier , Jon Masters , Christopher Covington , Thomas Gleixner , linux-arm-kernel@lists.infradead.org, G Gregory List-Id: linux-acpi@vger.kernel.org On Tue, Jan 17, 2017 at 06:18:12AM -0600, Timur Tabi wrote: > Fu Wei wrote: > >if (i >= ARCH_TIMER_MEM_MAX_FRAMES) { > > pr_err(FW_BUG "too many frames, ARMv8 spec only allows 8.\n"); > > pr_err(FW_BUG "too many frames, ARMv8 spec only allows %u.\n", > ARCH_TIMER_MEM_MAX_FRAMES); While I don't see ARCH_TIMER_MEM_MAX_FRAMES changing, this would be nicer to ensure the result obviously matches. As for wording, I'd perfer: pr_err(FW_BUG "too many frames, only %u are permitted.\n", ARCH_TIMER_MEM_MAX_FRAMES); ... so as to avoid any confusion between spec versions and so on. We can reconsider the message if/when that changes. Thanks, Mark.