From: James Liao <jamesjj.liao@mediatek.com>
To: Rob Herring <robh@kernel.org>
Cc: "Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@codeaurora.org>,
devicetree@vger.kernel.org,
"Prashant Gaikwad" <pgaikwad@nvidia.com>,
"Alexandre Torgue" <alexandre.torgue@st.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
linux-omap@vger.kernel.org, "Emilio López" <emilio@elopez.com.ar>,
"Peter De Schrijver" <pdeschrijver@nvidia.com>,
"Russell King" <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, "Tero Kristo" <t-kristo@ti.com>,
linux-tegra@vger.kernel.org, "Chen-Yu Tsai" <wens@csie.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
linux-mediatek@lists.infradead.org,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
linux-renesas-soc@vger.kernel.org,
"Matthias Brugger" <matthias.bgg@gmail.com>
Subject: Re: [PATCH] clk: Convert to using %pOF instead of full_name
Date: Wed, 19 Jul 2017 15:58:35 +0800 [thread overview]
Message-ID: <1500451115.30067.1.camel@mtksdaap41> (raw)
In-Reply-To: <20170718214339.7774-12-robh@kernel.org>
On Tue, 2017-07-18 at 16:42 -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.
>
> ---
> drivers/clk/mediatek/clk-cpumux.c | 2 +-
> drivers/clk/mediatek/clk-mtk.c | 2 +-
> drivers/clk/mediatek/reset.c | 2 +-
For clk/mediatek:
Acked-by: James Liao <jamesjj.liao@mediatek.com>
Best regards,
James
next prev parent reply other threads:[~2017-07-19 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 21:42 [PATCH] clk: Convert to using %pOF instead of full_name Rob Herring
2017-07-19 6:23 ` Maxime Ripard
[not found] ` <20170718214339.7774-12-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-07-19 7:44 ` Geert Uytterhoeven
2017-07-19 7:58 ` James Liao [this message]
2017-07-19 9:35 ` Alexandre Torgue
2017-07-19 10:24 ` Matthias Brugger
2017-07-21 22:49 ` Stephen Boyd
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=1500451115.30067.1.camel@mtksdaap41 \
--to=jamesjj.liao@mediatek.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=emilio@elopez.com.ar \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=t-kristo@ti.com \
--cc=thierry.reding@gmail.com \
--cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).