linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>
Cc: linux-clk <linux-clk@vger.kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 1/3 v3] dt-bindings: clock: Create YAML schema for ICST clocks
Date: Fri, 20 Mar 2020 13:59:12 +0100	[thread overview]
Message-ID: <CACRpkdafW8UsLXXXAvLzKZKr_R-dZbueyaAuo0GHupGXzstJ6A@mail.gmail.com> (raw)
In-Reply-To: <20200219103326.81120-1-linus.walleij@linaro.org>

On Wed, Feb 19, 2020 at 11:33 AM Linus Walleij <linus.walleij@linaro.org> wrote:

> The ICST clocks used in the ARM Integrator, Versatile and
> RealView platforms are updated to use YAML schema, and two
> new ICST clocks used by the Integrator IM-PD1 logical module
> are added in the process.
>
> Cc: devicetree@vger.kernel.org
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v2->v3:
> - Actually merge in the fix fixing the literal |
> ChangeLog v1->v2:
> - Add a literal | to preserve formatting in the bindings
> - Collect Rob's review tag

It's been a month, is it possible to merge this v3 patch set
so we can get some rotation in linux-next?

Yours,
Linus Walleij

  parent reply	other threads:[~2020-03-20 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 10:33 [PATCH 1/3 v3] dt-bindings: clock: Create YAML schema for ICST clocks Linus Walleij
2020-02-19 10:33 ` [PATCH 2/3 v3] clk: versatile: Export icst_clk_setup() Linus Walleij
2020-03-21  0:55   ` Stephen Boyd
2020-02-19 10:33 ` [PATCH 3/3 v3] clk: versatile: Add device tree probing for IM-PD1 clocks Linus Walleij
2020-03-21  0:56   ` Stephen Boyd
2020-03-20 12:59 ` Linus Walleij [this message]
2020-03-21  0:53 ` [PATCH 1/3 v3] dt-bindings: clock: Create YAML schema for ICST clocks Stephen Boyd
2020-03-21  0:55 ` 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=CACRpkdafW8UsLXXXAvLzKZKr_R-dZbueyaAuo0GHupGXzstJ6A@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    /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).