Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <1535471225.5357.0.camel@intel.com>
Subject: Re: [PATCH] nios2: Convert to using %pOFn instead of
 device_node.name
From:   Ley Foon Tan <ley.foon.tan@intel.com>
To:     Rob Herring <robh@kernel.org>, linux-kernel@vger.kernel.org
Cc:     Ley Foon Tan <lftan@altera.com>, nios2-dev@lists.rocketboards.org
Date:   Tue, 28 Aug 2018 23:47:05 +0800
In-Reply-To: <20180828015252.28511-5-robh@kernel.org>
References: <20180828015252.28511-1-robh@kernel.org>
         <20180828015252.28511-5-robh@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8BIT
Mime-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, 2018-08-27 at 20:52 -0500, Rob Herring wrote:
> In preparation to remove the node name pointer from struct
> device_node,
> convert printf users to use the %pOFn format specifier.
> 
> Cc: Ley Foon Tan <lftan@altera.com>
> Cc: nios2-dev@lists.rocketboards.org
> Signed-off-by: Rob Herring <robh@kernel.org>
Acked-by: Ley Foon Tan <ley.foon.tan@intel.com>

> ---
>  arch/nios2/kernel/time.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/nios2/kernel/time.c b/arch/nios2/kernel/time.c
> index ab88b6dd4679..54467d0085a1 100644
> --- a/arch/nios2/kernel/time.c
> +++ b/arch/nios2/kernel/time.c
> @@ -214,12 +214,12 @@ static int __init
> nios2_timer_get_base_and_freq(struct device_node *np,
>  {
>         *base = of_iomap(np, 0);
>         if (!*base) {
> -               pr_crit("Unable to map reg for %s\n", np->name);
> +               pr_crit("Unable to map reg for %pOFn\n", np);
>                 return -ENXIO;
>         }
> 
>         if (of_property_read_u32(np, "clock-frequency", freq)) {
> -               pr_crit("Unable to get %s clock frequency\n", np-
> >name);
> +               pr_crit("Unable to get %pOFn clock frequency\n", np);
>                 return -EINVAL;
>         }
> 
> --
> 2.17.1
> 
> 
> ________________________________
> 
> Confidentiality Notice.
> This message may contain information that is confidential or
> otherwise protected from disclosure. If you are not the intended
> recipient, you are hereby notified that any use, disclosure,
> dissemination, distribution, or copying of this message, or any
> attachments, is strictly prohibited. If you have received this
> message in error, please advise the sender by reply e-mail, and
> delete the message and any attachments. Thank you.