From: Stephen Boyd <sboyd@kernel.org>
To: Michael Tretter <m.tretter@pengutronix.de>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org
Cc: kernel@pengutronix.de,
Michael Turquette <mturquette@baylibre.com>,
Michal Simek <michal.simek@xilinx.com>,
Jolly Shah <jolly.shah@xilinx.com>
Subject: Re: [PATCH v2 0/4] clk: zynqmp: fix CLK_FRAC and various cleanups
Date: Thu, 11 Apr 2019 11:40:58 -0700 [thread overview]
Message-ID: <155500805844.20095.8423821269571777766@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20190404101621.7b88337c@litschi.hi.pengutronix.de>
Quoting Michael Tretter (2019-04-04 01:16:21)
> On Tue, 19 Mar 2019 11:01:43 +0100, Michael Tretter wrote:
> > This is v2 of the patchset to cleanup the ZynqMP clock driver.
>
> Gentle ping.
>
I could apply the first three, but the last one didn't work because
Jolly Shah sent some changes that wrecked it. Can you resend the last
patch reworked on top of it? You can use clk-zynq in clk.git if you need
something to base it upon.
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-zynq
next prev parent reply other threads:[~2019-04-11 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 10:01 [PATCH v2 0/4] clk: zynqmp: fix CLK_FRAC and various cleanups Michael Tretter
2019-03-19 10:01 ` [PATCH v2 1/4] clk: zynqmp: fix kerneldoc of __zynqmp_clock_get_parents Michael Tretter
2019-04-11 18:41 ` Stephen Boyd
2019-03-19 10:01 ` [PATCH v2 2/4] clk: zynqmp: do not export zynqmp_clk_register_* functions Michael Tretter
2019-04-11 18:41 ` Stephen Boyd
2019-03-19 10:01 ` [PATCH v2 3/4] clk: zynqmp: fix check for fractional clock Michael Tretter
2019-04-11 18:41 ` Stephen Boyd
2019-03-19 10:01 ` [PATCH v2 4/4] clk: zynqmp: use structs for clk query responses Michael Tretter
2019-04-04 8:16 ` [PATCH v2 0/4] clk: zynqmp: fix CLK_FRAC and various cleanups Michael Tretter
2019-04-11 18:40 ` Stephen Boyd [this message]
2019-04-12 9:36 ` Michael Tretter
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=155500805844.20095.8423821269571777766@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=jolly.shah@xilinx.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=michal.simek@xilinx.com \
--cc=mturquette@baylibre.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).