From: Yakir Yang <ykk@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Jeffy Chen <jeffy.chen@rock-chips.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 0/4] Add clock ids for RK3228 HDMI/VOP modules
Date: Fri, 26 Feb 2016 14:24:09 +0800 [thread overview]
Message-ID: <56CFEF89.7020003@rock-chips.com> (raw)
In-Reply-To: <2198453.NY4VYR4LaI@phil>
On 02/26/2016 09:14 AM, Heiko Stuebner wrote:
> Am Mittwoch, 24. Februar 2016, 18:05:03 schrieb Yakir Yang:
>> Add clocks ids for RK3228 HDMI/VOP modules which driver already have been
>> posted.
>>
>> RK3228 HDMI driver: https://patchwork.kernel.org/patch/7974671
>> RK3228 VOP driver: https://patchwork.kernel.org/patch/7952591
>>
>> Yakir Yang (4):
>> clk: rockchip: add the new clock ids for RK3228 VOP
>> clk: rockchip: set the clock ids for RK3228 VOP
>> clk: rockchip: add the new clock ids for RK3228 HDMI
>> clk: rockchip: set the clock ids for RK3228 HDMI
> applied all 4 to my clk-branch
Thanks
- Yakir
>
> Thanks
> Heiko
>
>
>
prev parent reply other threads:[~2016-02-26 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 10:05 [PATCH v1 0/4] Add clock ids for RK3228 HDMI/VOP modules Yakir Yang
2016-02-24 10:08 ` [PATCH v1 1/4] clk: rockchip: add the new clock ids for RK3228 VOP Yakir Yang
2016-02-24 10:14 ` [PATCH v1 3/4] clk: rockchip: add the new clock ids for RK3228 HDMI Yakir Yang
2016-02-24 10:16 ` [PATCH v1 4/4] clk: rockchip: set the " Yakir Yang
2016-02-24 10:54 ` [PATCH v1 2/4] clk: rockchip: set the clock ids for RK3228 VOP Yakir Yang
2016-02-26 1:14 ` [PATCH v1 0/4] Add clock ids for RK3228 HDMI/VOP modules Heiko Stuebner
2016-02-26 6:24 ` Yakir Yang [this message]
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=56CFEF89.7020003@rock-chips.com \
--to=ykk@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jeffy.chen@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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 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).