From: Stephen Boyd <sboyd@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
mturquette@baylibre.com, robh+dt@kernel.org,
xuwei5@hisilicon.com
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, amit.kucheria@linaro.org,
linux-clk@vger.kernel.org,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH 4/4] clk: hisilicon: Add clock driver for Hi3670 SoC
Date: Tue, 16 Oct 2018 14:49:15 -0700 [thread overview]
Message-ID: <153972655519.5275.5940549159000886799@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20180921060103.21370-5-manivannan.sadhasivam@linaro.org>
Quoting Manivannan Sadhasivam (2018-09-20 23:01:03)
> Add clock driver for HiSilicon Hi3670 SoC utilizing HiSilicon's
> common clk code.
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
Applied to clk-next
next prev parent reply other threads:[~2018-10-16 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 6:00 [PATCH 0/4] Add clock support for Hi3670 SoC Manivannan Sadhasivam
2018-09-21 6:01 ` [PATCH 1/4] dt-bindings: clk: hisilicon: Add bindings for Hi3670 clk Manivannan Sadhasivam
2018-10-16 21:49 ` Stephen Boyd
2018-09-21 6:01 ` [PATCH 2/4] arm64: dts: hisilicon: Add clock nodes for Hi3670 SoC Manivannan Sadhasivam
2018-11-29 15:21 ` Wei Xu
2018-09-21 6:01 ` [PATCH 3/4] arm64: dts: hisilicon: Source SoC clock for UART6 Manivannan Sadhasivam
2018-11-29 15:22 ` Wei Xu
2018-09-21 6:01 ` [PATCH 4/4] clk: hisilicon: Add clock driver for Hi3670 SoC Manivannan Sadhasivam
2018-10-16 21:49 ` Stephen Boyd [this message]
2018-10-12 3:38 ` [PATCH 0/4] Add clock support " Manivannan Sadhasivam
2018-10-12 16:03 ` Stephen Boyd
2018-10-12 16:08 ` Manivannan Sadhasivam
2018-10-17 3:27 ` Manivannan Sadhasivam
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=153972655519.5275.5940549159000886799@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=amit.kucheria@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=xuwei5@hisilicon.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 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).