devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v2 0/3] clk: Broadcom BCM63138 support
Date: Tue, 27 Oct 2015 14:08:38 -0700	[thread overview]
Message-ID: <20151027210838.GP19782@codeaurora.org> (raw)
In-Reply-To: <1445917997-3629-1-git-send-email-f.fainelli@gmail.com>

On 10/26, Florian Fainelli wrote:
> Hi all,
> 
> This patch series adds support for the Broadcom BCM63138 DSL SoCs
> clocking framework.
> 
> Since the HW is identical to the one found in Broadcom iProc SoCs, but the
> integration is different (obviously), there is still a new compatible string
> introduced just in case we happen to find issues in the future.
> 
> This applies on top of clk/next as of
> 679c51cffc3b316bd89ecc91ef92603dd6d4fc68 ("clk: Add stubs for of_clk_*() APIs when CONFIG_OF=n")
> 
> Since there is an obvious dependency between patch 2 and 3, we can either
> merge this through the Clock tree or via a future arm-soc pull requests
> for Broadcom SoCs.

One way to avoid the dependency would be to stage the first two
patches in clk tree under clk-bcm63xxx and then pull that into
your local branch via git FETCH && git checkout FETCH_HEAD and
then apply the 3rd patch on top, tag it and send it off to
arm-soc. This way, when arm-soc merges into linus' tree the
dependency is taken care of and we don't take anything for dtsi
files through the clk tree. It looks like nothing bad will happen
if patch 2 is merged before patch 3.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  parent reply	other threads:[~2015-10-27 21:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27  3:53 [PATCH v2 0/3] clk: Broadcom BCM63138 support Florian Fainelli
2015-10-27  3:53 ` [PATCH v2 1/3] clk: iproc: Extend binding to cover BCM63138 Florian Fainelli
2015-10-27  4:28   ` Rob Herring
2015-10-27  3:53 ` [PATCH v2 2/3] clk: bcm: Add BCM63138 clock support Florian Fainelli
2015-10-27 17:46   ` Stephen Boyd
2015-10-27 19:36     ` Florian Fainelli
2015-10-27 20:41       ` Stephen Boyd
2015-10-27  3:53 ` [PATCH v2 3/3] ARM: dts: BCM63xx: Add ARMPLL device tree nodes Florian Fainelli
2015-10-27  4:25 ` [PATCH v2 0/3] clk: Broadcom BCM63138 support Ray Jui
2015-10-27 21:08 ` Stephen Boyd [this message]
2015-10-27 23:50   ` Florian Fainelli

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=20151027210838.GP19782@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 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).