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 2/3] clk: bcm: Add BCM63138 clock support
Date: Tue, 27 Oct 2015 13:41:11 -0700 [thread overview]
Message-ID: <20151027204111.GO19782@codeaurora.org> (raw)
In-Reply-To: <562FD230.5090202@gmail.com>
On 10/27, Florian Fainelli wrote:
> On 27/10/15 10:46, Stephen Boyd wrote:
> > On 10/26, Florian Fainelli wrote:
> >> diff --git a/drivers/clk/bcm/Kconfig b/drivers/clk/bcm/Kconfig
> >> index 85260fb96b36..a0c18528b70d 100644
> >> --- a/drivers/clk/bcm/Kconfig
> >> +++ b/drivers/clk/bcm/Kconfig
> >> @@ -1,3 +1,13 @@
> >> +config CLK_BCM_63XX
> >> + bool "Broadcom BCM63xx clock support"
> >> + depends on ARCH_BCM_63XX || COMPILE_TEST
> >> + depends on COMMON_CLK
> >> + select COMMON_CLK_IPROC
> >> + default y
> >
> > perhaps default CLK_BCM_63XX?
>
> Did you mean default ARCH_BCM_63XX instead?
>
Yes.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-10-27 20:41 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 [this message]
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
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=20151027204111.GO19782@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).