From: Stephen Boyd <sboyd@kernel.org>
To: Tero Kristo <t-kristo@ti.com>, Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
mturquette@baylibre.com, s-anna@ti.com
Subject: Re: [PATCHv3 00/10] clk: ti: remoteproc / iommu support patches
Date: Mon, 28 Oct 2019 07:43:14 -0700 [thread overview]
Message-ID: <20191028144315.11CFA21721@mail.kernel.org> (raw)
In-Reply-To: <a88261a3-4012-1497-dd82-e41c0f328afd@ti.com>
Quoting Tero Kristo (2019-10-24 05:28:23)
> On 10/10/2019 18:32, Tero Kristo wrote:
> > On 10/10/2019 17:35, Tony Lindgren wrote:
> >> * Tero Kristo <t-kristo@ti.com> [191010 08:34]:
> >>> Stephen, any comments on this one or shall I just craft a
> >>> pull-request for
> >>> this and rest of the TI clock driver changes towards 5.5? There seems
> >>> to be
> >>> a pile of them coming this time over...
> >>
> >> Sounds like we need an immutable branch for the clkctrl related
> >> changes against v5.4-rc1 that I can also merge into omap-for-v5.5/prm
> >> branch in addition to the immutable prm reset driver branch.
> >>
> >> Otherwise I can't apply any of the consumer device related dts
> >> changes into that branch AFAIK.
> >
> > Well, the sgx patch you can probably merge, as it will fail silently and
> > only cause issues if you actually try to enable the device.
> >
> > However, yes I agree, we should probably setup an immutable branch here.
>
> Queued this series towards 5.5, thanks.
>
One minor comment. Otherwise looks fine. Thanks.
prev parent reply other threads:[~2019-10-28 14:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 13:26 [PATCHv3 00/10] clk: ti: remoteproc / iommu support patches Tero Kristo
2019-09-12 13:26 ` [PATCHv3 01/10] clk: ti: clkctrl: fix setting up clkctrl clocks Tero Kristo
2019-09-12 13:26 ` [PATCHv3 02/10] clk: ti: clkctrl: convert to use bit helper macros instead of bitops Tero Kristo
2019-09-12 13:26 ` [PATCHv3 03/10] clk: ti: clkctrl: add new exported API for checking standby info Tero Kristo
2019-10-28 14:40 ` Stephen Boyd
2019-10-31 13:51 ` Tero Kristo
2019-10-31 13:54 ` [PATCHv4 03/12] " Tero Kristo
2019-09-12 13:26 ` [PATCHv3 04/10] dt-bindings: clk: add omap5 iva clkctrl definitions Tero Kristo
2019-09-12 13:26 ` [PATCHv3 05/10] clk: ti: omap5: add IVA subsystem clkctrl data Tero Kristo
2019-09-12 13:26 ` [PATCHv3 06/10] clk: ti: dra7xx: Drop idlest polling from IPU & DSP clkctrl clocks Tero Kristo
2019-09-12 13:26 ` [PATCHv3 07/10] clk: ti: omap4: " Tero Kristo
2019-09-12 13:26 ` [PATCHv3 08/10] clk: ti: omap5: " Tero Kristo
2019-09-12 13:26 ` [PATCHv3 09/10] clk: ti: am43xx: drop idlest polling from pruss clkctrl clock Tero Kristo
2019-09-12 13:26 ` [PATCHv3 10/10] clk: ti: am33xx: " Tero Kristo
2019-10-10 8:34 ` [PATCHv3 00/10] clk: ti: remoteproc / iommu support patches Tero Kristo
2019-10-10 14:35 ` Tony Lindgren
2019-10-10 15:32 ` Tero Kristo
2019-10-24 12:28 ` Tero Kristo
2019-10-28 14:43 ` Stephen Boyd [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=20191028144315.11CFA21721@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=s-anna@ti.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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).