From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Convert to using %pOF instead of full_name
Date: Tue, 25 Jul 2017 13:04:23 +0100 [thread overview]
Message-ID: <20170725120422.GD27768@arm.com> (raw)
In-Reply-To: <20170718214339.7774-2-robh@kernel.org>
[adding Luc]
Hi Rob,
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 <robh@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: linux-arm-kernel at 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.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
luc.vanoostenryck@gmail.com
Subject: Re: [PATCH] arm64: Convert to using %pOF instead of full_name
Date: Tue, 25 Jul 2017 13:04:23 +0100 [thread overview]
Message-ID: <20170725120422.GD27768@arm.com> (raw)
In-Reply-To: <20170718214339.7774-2-robh@kernel.org>
[adding Luc]
Hi Rob,
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 <robh@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> 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.
Will
next prev parent reply other threads:[~2017-07-25 12:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 21:42 [PATCH] arm64: Convert to using %pOF instead of full_name Rob Herring
2017-07-18 21:42 ` Rob Herring
2017-07-18 21:42 ` Rob Herring
2017-07-25 12:04 ` Will Deacon [this message]
2017-07-25 12:04 ` Will Deacon
2017-07-26 0:27 ` Rob Herring
2017-07-26 0:27 ` Rob Herring
2017-07-26 0:27 ` Rob Herring
2017-07-26 12:02 ` Will Deacon
2017-07-26 12:02 ` Will Deacon
2017-07-26 12:14 ` Dan Carpenter
2017-07-26 12:14 ` Dan Carpenter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170725120422.GD27768@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.