From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-clk@vger.kernel.org, sboyd@kernel.org,
mturquette@baylibre.com, linux-omap@vger.kernel.org,
Andreas Kemnade <andreas@kemnade.info>
Subject: Re: [PATCH 0/4] clk: ti: get rid of CLK_IS_BASIC
Date: Mon, 21 Jan 2019 11:58:56 -0800 [thread overview]
Message-ID: <20190121195856.GI5544@atomide.com> (raw)
In-Reply-To: <b7571829-fb5e-c2be-59d1-b08d73bfca6d@ti.com>
* Tero Kristo <t-kristo@ti.com> [190115 18:32]:
> On 15/01/2019 20:20, Tony Lindgren wrote:
> > * Tero Kristo <t-kristo@ti.com> [190115 09:15]:
> > > Hi Stephen,
> > >
> > > As requested, this series gets rid of CLK_IS_BASIC flag usage from
> > > TI clock drivers.
> > >
> > > Boot tested on am3/am4/am5/omap3/omap4 series of SoCs. Also, ran a quick
> > > suspend/resume test on omap3/omap4/am5.
> >
> > Does this also fix the issue Andreas was fixing earlier
> > or is this separate clean-up?
>
> The series from Andreas would be needed on top of this.
OK so I acked Andreas' series, and here's an ack for
this series too:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2019-01-21 19:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 9:15 [PATCH 0/4] clk: ti: get rid of CLK_IS_BASIC Tero Kristo
2019-01-15 9:15 ` [PATCH 1/4] clk: ti: move clk_hw_omap list handling under generic part of the driver Tero Kristo
2019-01-15 9:15 ` [PATCH 2/4] clk: ti: add new API for checking if a provided clock is an OMAP clock Tero Kristo
2019-01-15 9:15 ` [PATCH 3/4] clk: ti: remove usage of CLK_IS_BASIC Tero Kristo
2019-01-15 9:15 ` [PATCH 4/4] clk: ti: generalize the init sequence of clk_hw_omap clocks Tero Kristo
2019-01-15 18:20 ` [PATCH 0/4] clk: ti: get rid of CLK_IS_BASIC Tony Lindgren
2019-01-15 18:31 ` Tero Kristo
2019-01-15 20:24 ` Andreas Kemnade
2019-01-21 19:58 ` Tony Lindgren [this message]
2019-02-15 19:19 ` Tero Kristo
2019-02-22 19:50 ` Stephen Boyd
2019-02-25 7:18 ` Tero Kristo
2019-02-25 17:12 ` Stephen Boyd
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=20190121195856.GI5544@atomide.com \
--to=tony@atomide.com \
--cc=andreas@kemnade.info \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=t-kristo@ti.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