From: Stephen Boyd <sboyd@codeaurora.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Peter De Schrijver <pdeschrijver@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-clk@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 3/4] clk: tegra: Use tegra_clk_register_periph_data()
Date: Thu, 2 Nov 2017 01:16:53 -0700 [thread overview]
Message-ID: <20171102081653.GL11011@codeaurora.org> (raw)
In-Reply-To: <20170901145343.19890-3-thierry.reding@gmail.com>
On 09/01, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Instead of open-coding the same pattern repeatedly, reuse the newly
> introduced tegra_clk_register_periph_data() helper that will unpack
> the initialization structure.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Michael Turquette
<mturquette-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>,
Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Jonathan Hunter
<jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
linux-clk-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/4] clk: tegra: Use tegra_clk_register_periph_data()
Date: Thu, 2 Nov 2017 01:16:53 -0700 [thread overview]
Message-ID: <20171102081653.GL11011@codeaurora.org> (raw)
In-Reply-To: <20170901145343.19890-3-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On 09/01, Thierry Reding wrote:
> From: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> Instead of open-coding the same pattern repeatedly, reuse the newly
> introduced tegra_clk_register_periph_data() helper that will unpack
> the initialization structure.
>
> Signed-off-by: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-11-02 8:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 14:53 [PATCH 1/4] dt-bindings: clock: tegra: Add sor1_out clock Thierry Reding
2017-09-01 14:53 ` Thierry Reding
2017-09-01 14:53 ` [PATCH 2/4] clk: tegra: Add peripheral clock registration helper Thierry Reding
2017-11-02 8:16 ` Stephen Boyd
2017-11-02 8:16 ` Stephen Boyd
2017-09-01 14:53 ` [PATCH 3/4] clk: tegra: Use tegra_clk_register_periph_data() Thierry Reding
2017-09-01 14:53 ` Thierry Reding
2017-11-02 8:16 ` Stephen Boyd [this message]
2017-11-02 8:16 ` Stephen Boyd
2017-09-01 14:53 ` [PATCH 4/4] clk: tegra: Fix sor1_out clock implementation Thierry Reding
2017-09-01 14:53 ` Thierry Reding
2017-11-02 8:16 ` Stephen Boyd
2017-11-02 8:16 ` [PATCH 1/4] dt-bindings: clock: tegra: Add sor1_out clock Stephen Boyd
2017-11-02 8:16 ` Stephen Boyd
2017-11-02 8:46 ` Thierry Reding
2017-11-02 8:46 ` Thierry Reding
2017-11-03 15:16 ` Stephen Boyd
2017-11-03 15:16 ` 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=20171102081653.GL11011@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=jonathanh@nvidia.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=pdeschrijver@nvidia.com \
--cc=thierry.reding@gmail.com \
/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.