linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>,
	Michael Turquette <mturquette@baylibre.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Antoine Tenart <antoine.tenart@bootlin.com>,
	Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Nadav Haklai <nadavh@marvell.com>,
	Grzegorz Jaszczyk <jaz@semihalf.com>,
	Marcin Wojtas <mw@semihalf.com>,
	Stefan Chulski <stefanc@marvell.com>,
	Yan Markman <ymarkman@marvell.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: [PATCH 0/8] AP807 clocks support
Date: Tue, 17 Sep 2019 22:07:19 -0700	[thread overview]
Message-ID: <20190918050720.B390B214AF@mail.kernel.org> (raw)
In-Reply-To: <20190805100310.29048-1-miquel.raynal@bootlin.com>

Quoting Miquel Raynal (2019-08-05 03:03:02)
> Hello,
> 
> This is the first batch of changes (out of three) to support the brand
> new Marvell CN9130 SoCs which are made of one AP807 and one CP115.
> 
> This clock series applies on top of Gregory's "AP806 CPU clocks" [1].
> 
> [1] https://patchwork.kernel.org/cover/11038577/

Ugh I found this series stashed away and never merged to clk-next.


  parent reply	other threads:[~2019-09-18  5:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 10:03 [PATCH 0/8] AP807 clocks support Miquel Raynal
2019-08-05 10:03 ` [PATCH 1/8] dt-bindings: ap80x: Document AP807 CPU clock compatible Miquel Raynal
2019-08-21 18:51   ` Rob Herring
2019-09-18  5:08   ` Stephen Boyd
2019-08-05 10:03 ` [PATCH 2/8] dt-bindings: ap806: Document AP807 " Miquel Raynal
2019-08-21 18:51   ` Rob Herring
2019-09-18  5:08   ` Stephen Boyd
2019-08-05 10:03 ` [PATCH 3/8] clk: mvebu: ap806-cpu: prepare mapping of AP807 CPU clock Miquel Raynal
2019-09-18  5:08   ` Stephen Boyd
2019-08-05 10:03 ` [PATCH 4/8] clk: mvebu: ap80x-cpu: add AP807 CPU clock support Miquel Raynal
2019-09-18  5:08   ` Stephen Boyd
2019-08-05 10:03 ` [PATCH 5/8] clk: mvebu: ap806: be more explicit on what SaR is Miquel Raynal
2019-09-18  5:08   ` Stephen Boyd
2019-08-05 10:03 ` [PATCH 6/8] clk: mvebu: ap806: add AP-DCLK (hclk) to system controller driver Miquel Raynal
2019-09-18  5:08   ` Stephen Boyd
2019-08-05 10:03 ` [PATCH 7/8] clk: mvebu: ap806: Prepare the introduction of AP807 clock support Miquel Raynal
2019-09-18  5:08   ` Stephen Boyd
2019-08-05 10:03 ` [PATCH 8/8] clk: mvebu: ap80x: add " Miquel Raynal
2019-09-18  5:08   ` Stephen Boyd
2019-09-18  5:07 ` Stephen Boyd [this message]
2019-09-20  8:01   ` [PATCH 0/8] AP807 clocks support Miquel Raynal

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=20190918050720.B390B214AF@mail.kernel.org \
    --to=sboyd@kernel.org \
    --cc=antoine.tenart@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=jaz@semihalf.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=mturquette@baylibre.com \
    --cc=mw@semihalf.com \
    --cc=nadavh@marvell.com \
    --cc=robh+dt@kernel.org \
    --cc=stefanc@marvell.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=ymarkman@marvell.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).