linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-clk@vger.kernel.org, linux-omap@vger.kernel.org,
	sboyd@kernel.org, mturquette@baylibre.com
Subject: Re: [PATCH 2/6] ARM: omap2+: hwmod: drop CLK_IS_BASIC flag usage
Date: Thu, 4 Apr 2019 07:06:58 -0700	[thread overview]
Message-ID: <20190404140658.GB49658@atomide.com> (raw)
In-Reply-To: <1554365467-1325-3-git-send-email-t-kristo@ti.com>

* Tero Kristo <t-kristo@ti.com> [190404 08:12]:
> CLK_IS_BASIC flag is about to get deprecated, and as such, can't be used.
> Instead, the API call for checking whether a clock is of type hw_omap shall
> be used, so convert the code to use this.

Acked-by: Tony Lindgren <tony@atomide.com>

  reply	other threads:[~2019-04-04 14:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04  8:11 [PATCH 0/6] clk: ti: a few OMAP clock fixes Tero Kristo
2019-04-04  8:11 ` [PATCH 1/6] clk: ti: export the omap2_clk_is_hw_omap call Tero Kristo
2019-04-25 18:15   ` Stephen Boyd
2019-04-04  8:11 ` [PATCH 2/6] ARM: omap2+: hwmod: drop CLK_IS_BASIC flag usage Tero Kristo
2019-04-04 14:06   ` Tony Lindgren [this message]
2019-04-25 18:15   ` Stephen Boyd
2019-04-04  8:11 ` [PATCH 3/6] clk: ti: dra7x: prevent non-existing clkctrl clocks from registering Tero Kristo
2019-04-25 18:15   ` Stephen Boyd
2019-04-04  8:11 ` [PATCH 4/6] clk: ti: dra7: disable the RNG and TIMER12 clkctrl clocks on HS devices Tero Kristo
2019-04-25 18:15   ` Stephen Boyd
2019-04-04  8:11 ` [PATCH 5/6] clk: ti: am33xx: drop idlest polling from gfx clkctrl clock Tero Kristo
2019-04-04 14:06   ` Tony Lindgren
2019-04-08  5:45     ` Tero Kristo
2019-04-25 17:51       ` Stephen Boyd
2019-04-25 17:56         ` Tony Lindgren
2019-04-04  8:11 ` [PATCH 6/6] clk: ti: am43xx: " Tero Kristo

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=20190404140658.GB49658@atomide.com \
    --to=tony@atomide.com \
    --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;
as well as URLs for NNTP newsgroup(s).