From: Stephen Boyd <sboyd@codeaurora.org>
To: Jiancheng Xue <xuejiancheng@hisilicon.com>
Cc: robh+dt@kernel.org, kishon@ti.com, xuwei5@hisilicon.com,
catalin.marinas@arm.com, balbi@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, project-aspen-dev@linaro.org,
yanhaifeng@hisilicon.com
Subject: Re: [PATCH 1/5] clk: hisilicon: add usb2 clocks for hi3798cv200 SoC
Date: Wed, 21 Jun 2017 10:46:51 -0700 [thread overview]
Message-ID: <20170621174651.GC4493@codeaurora.org> (raw)
In-Reply-To: <1498035645-22804-2-git-send-email-xuejiancheng@hisilicon.com>
On 06/21, Jiancheng Xue wrote:
> Add usb2 clocks for hi3798cv200 SoC.
>
> Signed-off-by: Jiancheng Xue <xuejiancheng@hisilicon.com>
> Reviewed-by: Daniel Thompson <daniel.thompson@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-21 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 9:00 [PATCH 0/5] enable usb2 function on poplar board Jiancheng Xue
2017-06-21 9:00 ` [PATCH 1/5] clk: hisilicon: add usb2 clocks for hi3798cv200 SoC Jiancheng Xue
2017-06-21 17:46 ` Stephen Boyd [this message]
[not found] ` <1498035645-22804-1-git-send-email-xuejiancheng-C8/M+/jPZTeaMJb+Lgu22Q@public.gmane.org>
2017-06-21 9:00 ` [PATCH 2/5] dt-bindings: phy-hisi-inno-usb2: add support for hisi-inno-usb2 phy Jiancheng Xue
2017-06-22 8:23 ` Jiancheng Xue
2017-06-26 15:56 ` Rob Herring
2017-06-21 9:00 ` [PATCH 3/5] phy: add inno-usb2-phy driver for hi3798cv200 SoC Jiancheng Xue
2017-06-21 10:52 ` [project-aspen-dev] " Daniel Thompson
2017-06-21 9:00 ` [PATCH 4/5] arm64: dts: hisilicon: add usb2 controller and phy nodes for poplar board Jiancheng Xue
2017-06-21 9:00 ` [PATCH 5/5] arm64: defconfig: enable some drivers and configs for hi3798cv200-poplar board Jiancheng Xue
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=20170621174651.GC4493@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=balbi@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=project-aspen-dev@linaro.org \
--cc=robh+dt@kernel.org \
--cc=xuejiancheng@hisilicon.com \
--cc=xuwei5@hisilicon.com \
--cc=yanhaifeng@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).