From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Deacon Subject: Re: [PATCH] arm64: Convert to using %pOF instead of full_name Date: Wed, 26 Jul 2017 13:02:33 +0100 Message-ID: <20170726120233.GC2115@arm.com> References: <20170718214339.7774-2-robh@kernel.org> <20170725120422.GD27768@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: Catalin Marinas , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , luc.vanoostenryck@gmail.com, dan.carpenter@oracle.com List-Id: devicetree@vger.kernel.org Hi Rob, On Tue, Jul 25, 2017 at 07:27:29PM -0500, Rob Herring wrote: > On Tue, Jul 25, 2017 at 7:04 AM, Will Deacon wrote: > > On Tue, Jul 18, 2017 at 04:42:42PM -0500, Rob Herring wrote: > >> Now that we have a custom printf format specifier, convert users of > >> full_name to use %pOF instead. This is preparation to remove storing > >> of the full path string for each node. > >> > >> Signed-off-by: Rob Herring > >> Cc: Catalin Marinas > >> Cc: Will Deacon > >> Cc: linux-arm-kernel@lists.infradead.org > >> --- > >> arch/arm64/kernel/cpu_ops.c | 4 ++-- > >> arch/arm64/kernel/smp.c | 12 ++++++------ > >> arch/arm64/kernel/topology.c | 22 +++++++++++----------- > >> 3 files changed, 19 insertions(+), 19 deletions(-) > > > > I've queued this and the perf patch too, but it would be good if somebody > > could update sparse to recognise this format specifier. Currently it > > just complains about it. > > I'm happy to fix it, but I ran sparse and don't see any errors. Got a pointer? I went back and checked again and it's not sparse that's warning, it's actually smatch (sorry for getting that mixed up): arch/arm64/kernel/cpu_ops.c:85 cpu_read_enable_method() error: unrecognized %p extension 'O', treated as normal %p [smatch] Will