All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Maxime Ripard <maxime.ripard@free-electrons.com>,
	Chen-Yu Tsai <wens@csie.org>, Heiko Stuebner <heiko@sntech.de>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
	linux-rockchip@lists.infradead.org, linux-tegra@vger.kernel.org,
	linux-clk@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/3] Use of_clk_get_parent_count() instead of open coding
Date: Fri, 19 Jan 2018 16:18:18 +0100	[thread overview]
Message-ID: <1516375101-29836-1-git-send-email-geert+renesas@glider.be> (raw)

	Hi all,

This patch series replaces open-coded versions of
of_clk_get_parent_count() by calls to the helper function.

These patches are independent, so they can be applied where appropriate.
Thanks!

Geert Uytterhoeven (3):
  pinctrl: sunxi: Use of_clk_get_parent_count() instead of open coding
  soc: rockchip: power-domain: Use of_clk_get_parent_count() instead of
    open coding
  soc/tegra: pmc: Use of_clk_get_parent_count() instead of open coding

 drivers/pinctrl/sunxi/pinctrl-sunxi.c | 3 ++-
 drivers/soc/rockchip/pm_domains.c     | 3 ++-
 drivers/soc/tegra/pmc.c               | 3 ++-
 3 files changed, 6 insertions(+), 3 deletions(-)

-- 
2.7.4

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

             reply	other threads:[~2018-01-19 15:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 15:18 Geert Uytterhoeven [this message]
2018-01-19 15:18 ` [PATCH 2/3] soc: rockchip: power-domain: Use of_clk_get_parent_count() instead of open coding Geert Uytterhoeven
2018-01-19 15:18   ` Geert Uytterhoeven
2018-02-10 16:35   ` Heiko Stuebner
2018-02-10 16:35     ` Heiko Stuebner
2018-02-18 19:09     ` Michael Turquette
2018-02-18 19:09       ` Michael Turquette
2018-02-18 19:09       ` Michael Turquette
2018-03-02 13:15       ` Geert Uytterhoeven
2018-03-02 13:15         ` Geert Uytterhoeven
2018-03-02 13:15         ` Geert Uytterhoeven
2018-03-12 22:32         ` Stephen Boyd
2018-03-12 22:32           ` Stephen Boyd
2018-03-12 22:32           ` Stephen Boyd
     [not found] ` <1516375101-29836-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2018-01-19 15:18   ` [PATCH 1/3] pinctrl: sunxi: " Geert Uytterhoeven
2018-01-19 15:18     ` Geert Uytterhoeven
2018-01-22  8:55     ` Linus Walleij
2018-01-22  8:55       ` Linus Walleij
2018-01-19 15:18   ` [PATCH 3/3] soc/tegra: pmc: " Geert Uytterhoeven
2018-01-19 15:18     ` Geert Uytterhoeven
2018-01-19 15:18     ` Geert Uytterhoeven

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=1516375101-29836-1-git-send-email-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --cc=heiko@sntech.de \
    --cc=jonathanh@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.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 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.