From: Michal Simek <michal.simek@xilinx.com>
To: Mike Turquette <mturquette@ti.com>,
Josh Cartwright <josh.cartwright@ni.com>
Cc: Soren Brinkmann <sorenb@xilinx.com>,
Rob Herring <rob.herring@calxeda.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
John Linn <linnj@xilinx.com>, "arm@kernel.org" <arm@kernel.org>
Subject: RE: [PATCH v3] clk: Add support for fundamental zynq clks
Date: Wed, 14 Nov 2012 15:14:07 +0000 [thread overview]
Message-ID: <e71b86f3-58fe-4785-9f9d-bbade8aa7afb@AM1EHSMHS013.ehs.local> (raw)
In-Reply-To: <20121113235516.20034.31067@nucleus>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1246 bytes --]
> -----Original Message-----
> From: Mike Turquette [mailto:mturquette@ti.com]
> Sent: Wednesday, November 14, 2012 12:55 AM
> To: Josh Cartwright; Michal Simek
> Cc: Soren Brinkmann; Rob Herring; linux-kernel@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; John Linn; arm@kernel.org
> Subject: Re: [PATCH v3] clk: Add support for fundamental zynq clks
>
> Quoting Josh Cartwright (2012-11-13 15:26:48)
> > Provide simplified models for the necessary clocks on the zynq-7000
> > platform. Currently, the PLLs, the CPU clock network, and the basic
> > peripheral clock networks (for SDIO, SMC, SPI, QSPI, UART) are modelled.
> >
> > OF bindings are also provided and documented.
> >
> > Signed-off-by: Josh Cartwright <josh.cartwright@ni.com>
> > ---
> > Michal-
> >
> > Here is a v3 with a fix for the problem Soren Brinkmann spotted. Am I
> > correct that your current plan is to merge this into your tree?
> >
> > If so:
> >
> > Mike-
> >
> > Can we get your Acked-by on this one?
> >
>
> Acked-by: Mike Turquette <mturquette@linaro.org>
Applied.
Thanks,
Michal
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2012-11-14 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 18:49 [PATCH v2 0/5] zynq clk support Josh Cartwright
2012-10-31 18:24 ` [PATCH v2 1/5] ARM: zynq: dts: split up device tree Josh Cartwright
2012-11-12 12:00 ` Michal Simek
2012-10-31 18:58 ` [PATCH v2 2/5] clk: Add support for fundamental zynq clks Josh Cartwright
2012-11-08 23:28 ` Soren Brinkmann
2012-11-13 22:02 ` Josh Cartwright
2012-11-14 15:12 ` Michal Simek
2012-11-13 23:26 ` [PATCH v3] " Josh Cartwright
2012-11-13 23:55 ` Mike Turquette
2012-11-14 15:14 ` Michal Simek [this message]
[not found] ` <20121108232807.GG18904@xsjpsgb1010.xilinx.com>
2012-11-12 11:57 ` [PATCH v2 2/5] " Michal Simek
2012-10-31 19:28 ` [PATCH v2 4/5] serial: xilinx_uartps: get clock rate info from dts Josh Cartwright
2012-10-31 19:56 ` [PATCH v2 5/5] ARM: zynq: add clk binding support to the ttc Josh Cartwright
2012-11-08 18:04 ` [PATCH v2 3/5] ARM: zynq: use zynq clk bindings Josh Cartwright
2012-11-08 23:38 ` [PATCH v2 0/5] zynq clk support Soren Brinkmann
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=e71b86f3-58fe-4785-9f9d-bbade8aa7afb@AM1EHSMHS013.ehs.local \
--to=michal.simek@xilinx.com \
--cc=arm@kernel.org \
--cc=josh.cartwright@ni.com \
--cc=linnj@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=rob.herring@calxeda.com \
--cc=sorenb@xilinx.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
all inboxes | Powered by JetHome®