From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
devicetree@vger.kernel.org, patchwork-bot+notify@kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2 1/4] dt-bindings: amlogic: add new compatible devices to clk_measure
Date: Fri, 18 Jan 2019 22:56:40 +0100 [thread overview]
Message-ID: <CAFBinCDzvQ6BhkQmCt+OJs7L+xydq7QVy5QB6MYBFaAc3fzpmg@mail.gmail.com> (raw)
In-Reply-To: <20190118103423.15075-2-jbrunet@baylibre.com>
On Fri, Jan 18, 2019 at 11:34 AM Jerome Brunet <jbrunet@baylibre.com> wrote:
>
> Add the axg and g12a SoC family compatible to the clock measure bindings
>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
this is certainly going to make it easier to fix potential issues with
the clock controller drivers!
Regards
Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-01-18 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 10:34 [PATCH v2 0/4] soc: amlogic: clk-measure: add axg and g12a support Jerome Brunet
2019-01-18 10:34 ` [PATCH v2 1/4] dt-bindings: amlogic: add new compatible devices to clk_measure Jerome Brunet
2019-01-18 21:56 ` Martin Blumenstingl [this message]
2019-01-21 17:11 ` Rob Herring
2019-01-18 10:34 ` [PATCH v2 2/4] soc: amlogic: clk-measure: add axg and g12a support Jerome Brunet
2019-01-18 21:53 ` Martin Blumenstingl
2019-01-18 10:34 ` [PATCH v2 3/4] arm64: dts: meson: axg: add clk measure support Jerome Brunet
2019-01-18 21:57 ` Martin Blumenstingl
2019-01-18 10:34 ` [PATCH v2 4/4] arm64: dts: meson: g12a: " Jerome Brunet
2019-01-18 21:59 ` Martin Blumenstingl
2019-01-18 10:52 ` [PATCH v2 0/4] soc: amlogic: clk-measure: add axg and g12a support Neil Armstrong
2019-02-07 3:38 ` Kevin Hilman
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=CAFBinCDzvQ6BhkQmCt+OJs7L+xydq7QVy5QB6MYBFaAc3fzpmg@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+notify@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).