From: Stephen Boyd <sboyd@codeaurora.org>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Baoyou Xie <xie.baoyou@sanechips.com.cn>,
Xin Zhou <zhou.xin8@sanechips.com.cn>,
Jun Nie <jun.nie@linaro.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH] clk: zx296718: export I2S mux clocks
Date: Mon, 19 Jun 2017 18:02:58 -0700 [thread overview]
Message-ID: <20170620010258.GJ20170@codeaurora.org> (raw)
In-Reply-To: <1497709265-22944-1-git-send-email-shawnguo@kernel.org>
On 06/17, Shawn Guo wrote:
> From: Shawn Guo <shawn.guo@linaro.org>
>
> Export I2S mux clocks, so that device tree can refer to them for setting
> a better parent clock for I2S work clock.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
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: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: zx296718: export I2S mux clocks
Date: Mon, 19 Jun 2017 18:02:58 -0700 [thread overview]
Message-ID: <20170620010258.GJ20170@codeaurora.org> (raw)
In-Reply-To: <1497709265-22944-1-git-send-email-shawnguo@kernel.org>
On 06/17, Shawn Guo wrote:
> From: Shawn Guo <shawn.guo@linaro.org>
>
> Export I2S mux clocks, so that device tree can refer to them for setting
> a better parent clock for I2S work clock.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.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-06-20 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 14:21 [PATCH] clk: zx296718: export I2S mux clocks Shawn Guo
2017-06-17 14:21 ` Shawn Guo
2017-06-20 1:02 ` Stephen Boyd [this message]
2017-06-20 1:02 ` 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=20170620010258.GJ20170@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=shawn.guo@linaro.org \
--cc=shawnguo@kernel.org \
--cc=xie.baoyou@sanechips.com.cn \
--cc=zhou.xin8@sanechips.com.cn \
/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.