From: Stephen Boyd <sboyd@codeaurora.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-clk@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, jonmason@broadcom.com,
mturquette@baylibre.com, linux@arm.linux.org.uk,
sbranden@broadcom.com, rjui@broadcom.com
Subject: Re: [PATCH v4 1/3] clk: iproc: Extend binding to cover BCM63138
Date: Fri, 20 Nov 2015 15:48:24 -0800 [thread overview]
Message-ID: <20151120234824.GC9555@codeaurora.org> (raw)
In-Reply-To: <1446168199-5959-2-git-send-email-f.fainelli@gmail.com>
On 10/29, Florian Fainelli wrote:
> Broadcom BCM63138 DSL SoCs have the same ARMPLL clocking infrastructure
> as the Cygnus and iProc chips, add a dedicated compatible string and
> document that the ARMPLL node is a valid node for this chip.
>
> Acked-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
Applied to clk-bcm63xx
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-11-20 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 1:23 [PATCH v4 0/3] clk: Broadcom BCM63138 support Florian Fainelli
2015-10-30 1:23 ` [PATCH v4 1/3] clk: iproc: Extend binding to cover BCM63138 Florian Fainelli
2015-11-20 23:48 ` Stephen Boyd [this message]
2015-10-30 1:23 ` [PATCH v4 2/3] clk: bcm: Add BCM63138 clock support Florian Fainelli
2015-11-20 23:48 ` Stephen Boyd
2015-10-30 1:23 ` [PATCH v4 3/3] ARM: dts: BCM63xx: Add ARMPLL device tree nodes Florian Fainelli
2015-11-23 18:40 ` Florian Fainelli
2015-11-23 18:40 ` Florian Fainelli
2015-11-20 1:00 ` [PATCH v4 0/3] clk: Broadcom BCM63138 support Florian Fainelli
2015-11-20 1:02 ` Florian Fainelli
2015-11-20 18:46 ` Stephen Boyd
2015-11-20 18:47 ` Florian Fainelli
2015-11-20 23:49 ` 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=20151120234824.GC9555@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonmason@broadcom.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@baylibre.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.