From: Florian Fainelli <f.fainelli@gmail.com>
To: Ray Jui <ray.jui@broadcom.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Pramod Kumar <pramod.kumar@broadcom.com>
Subject: Re: [PATCH v3 3/3] arm64: dts: Update Stingray clock DT nodes
Date: Mon, 4 Jun 2018 14:11:18 -0700 [thread overview]
Message-ID: <9305e486-9c67-0fca-7fd8-c954ee0d8c6f@gmail.com> (raw)
In-Reply-To: <1527900968-12017-4-git-send-email-ray.jui@broadcom.com>
On 06/01/2018 05:56 PM, Ray Jui wrote:
> From: Pramod Kumar <pramod.kumar@broadcom.com>
>
> Update clock output names in the Stingray clock DT nodes so they match
> the binding document and the latest ASIC datasheet. Also add entries
> for LCPLL2
>
> Signed-off-by: Pramod Kumar <pramod.kumar@broadcom.com>
> Signed-off-by: Ray Jui <ray.jui@broadcom.com>
Applied to devicetree-arm64/next, thanks!
--
Florian
prev parent reply other threads:[~2018-06-04 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 0:56 [PATCH v3 0/3] Update Broadcom Stingray clock entries Ray Jui
2018-06-02 0:56 ` [PATCH v3 1/3] dt-bindings: clk: Update Stingray binding doc Ray Jui
2018-06-02 6:26 ` Stephen Boyd
2018-06-02 0:56 ` [PATCH v3 2/3] clk: bcm: Update and add Stingray clock entries Ray Jui
2018-06-02 6:26 ` Stephen Boyd
2018-06-02 0:56 ` [PATCH v3 3/3] arm64: dts: Update Stingray clock DT nodes Ray Jui
2018-06-04 21:11 ` Florian Fainelli [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=9305e486-9c67-0fca-7fd8-c954ee0d8c6f@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pramod.kumar@broadcom.com \
--cc=ray.jui@broadcom.com \
--cc=robh+dt@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).