From: James Liao <jamesjj.liao@mediatek.com>
To: John Crispin <blogic@openwrt.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
devicetree@vger.kernel.org, Sascha Hauer <kernel@pengutronix.de>,
srv_heupstream@mediatek.com, linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/6] Add clock support for Mediatek MT2701
Date: Wed, 13 Jan 2016 11:01:46 +0800 [thread overview]
Message-ID: <1452654106.2657.0.camel@mtksdaap41> (raw)
In-Reply-To: <5694D106.2030009@openwrt.org>
Hi John,
On Tue, 2016-01-12 at 11:10 +0100, John Crispin wrote:
> Hi James,
>
> On 12/01/2016 09:31, James Liao wrote:
> > This patchset is based on 4.4-rc7, add clock and reset controller support
> > for Mediatek MT2701.
> >
> > This patchset also refined makefile and Kconfig to support configurable
> > multiple SoC clock support.
> >
> > changes since v2:
> > - Fix ethsys definition.
> > - Replace read-modify-write with regmap_update_bits() in clock operations.
> > - Move mt2701-resets.h to include/dt-bindings/reset/.
> > - Add hifsys reset patch from John Crispin.
>
> thanks for folding the fixup.
>
> i have been testing your V2 on MT7623 for several days now and updated
> to V3 this morning which works just as well. feel free to add
>
> Tested-by: John Crispin <blogic@openwrt.org>
Thanks for your help.
Best regards,
James
prev parent reply other threads:[~2016-01-13 3:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 8:31 [PATCH v3 0/6] Add clock support for Mediatek MT2701 James Liao
2016-01-12 8:31 ` [PATCH v3 1/6] clk: mediatek: Refine the makefile to support multiple clock drivers James Liao
[not found] ` <1452587470-61506-2-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2016-01-21 2:28 ` Yingjoe Chen
2016-01-21 2:45 ` Yingjoe Chen
2016-01-21 5:50 ` James Liao
2016-01-21 5:49 ` James Liao
2016-01-12 8:31 ` [PATCH v3 2/6] dt-bindings: ARM: Mediatek: Document bindings for MT2701 James Liao
2016-01-13 2:10 ` Rob Herring
[not found] ` <1452587470-61506-1-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2016-01-12 8:31 ` [PATCH v3 3/6] clk: mediatek: Add dt-bindings for MT2701 clocks James Liao
2016-01-13 19:29 ` Michael Turquette
2016-01-12 8:31 ` [PATCH v3 4/6] clk: mediatek: Add MT2701 clock support James Liao
2016-01-12 8:31 ` [PATCH v3 5/6] reset: mediatek: Add MT2701 reset controller dt-binding file James Liao
[not found] ` <1452587470-61506-6-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2016-01-12 10:22 ` Philipp Zabel
2016-01-12 8:31 ` [PATCH v3 6/6] reset: mediatek: Add MT2701 reset driver James Liao
2016-01-12 10:22 ` Philipp Zabel
2016-01-12 10:10 ` [PATCH v3 0/6] Add clock support for Mediatek MT2701 John Crispin
2016-01-13 3:01 ` James Liao [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=1452654106.2657.0.camel@mtksdaap41 \
--to=jamesjj.liao@mediatek.com \
--cc=blogic@openwrt.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=sboyd@codeaurora.org \
--cc=srv_heupstream@mediatek.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).