Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756030AbcLNQgH (ORCPT ); Wed, 14 Dec 2016 11:36:07 -0500 Received: from mx1.redhat.com ([209.132.183.28]:59386 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754216AbcLNQgE (ORCPT ); Wed, 14 Dec 2016 11:36:04 -0500 Subject: Re: [PATCH 1/1] arm64: Correcting format specifier for printing 64 bit addresses To: Christoffer Dall , Maninder Singh References: <1480925393-8386-1-git-send-email-maninder1.s@samsung.com> <20161206161116.GD4816@cbox> Cc: catalin.marinas@arm.com, will.deacon@arm.com, marc.zyngier@arm.com, rkrcmar@redhat.com, cmetcalf@mellanox.com, panand@redhat.com, mark.rutland@arm.com, james.morse@arm.com, akpm@linux-foundation.org, sandeepa.s.prabhu@gmail.com, labbott@redhat.com, shijie.huang@arm.com, ard.biesheuvel@linaro.org, wangkefeng.wang@huawei.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, pankaj.m@samsung.com, ajeet.y@samsung.com, cpgs@samsung.com, Vaneet Narang From: Paolo Bonzini Message-ID: <65935935-bdd9-c6a6-1a33-2bbaf6ffbbc5@redhat.com> Date: Wed, 14 Dec 2016 17:35:53 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20161206161116.GD4816@cbox> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Wed, 14 Dec 2016 16:36:01 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 525 Lines: 17 On 06/12/2016 17:11, Christoffer Dall wrote: > + kvm_err("Unsupported guest CP%d access at: %08lx\n", > + cp, *vcpu_pc(vcpu)); > + else > + kvm_err("Unsupported guest CP%d access at: %016lx\n", > + cp, *vcpu_pc(vcpu)); > > It feels a bit much to me to have an if-statement to differentiate the > number of leading zeros, so if it's important to always have fixed > widths then I would just use %016lx in both cases. Really, this is just a debugging message. Just use "0x%lx" and let's stop bikeshedding. :) Paolo