From: Florian Fainelli <fainelli@broadcom.com>
To: Jon Mason <jonmason@broadcom.com>, Scott Branden <sbranden@broadcom.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Florian Fainelli <f.fainelli@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>, Ray Jui <rjui@broadcom.com>,
<linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH] clk: iproc: Make clocks visible options
Date: Thu, 22 Oct 2015 14:57:49 -0700 [thread overview]
Message-ID: <56295BDD.4000609@broadcom.com> (raw)
In-Reply-To: <20151022201433.GK651@broadcom.com>
On 22/10/15 13:14, Jon Mason wrote:
> On Thu, Oct 22, 2015 at 12:46:46PM -0700, Scott Branden wrote:
>> Hi Jon,
>>
>> comments inline.
>>
>> On 15-10-22 12:25 PM, Jon Mason wrote:
>>> Make the clocks visible options that can be selected by anyone. This
>>> avoids the problems of:
>>> 1) Select is a reverse dependency and is hard for people to understand
>>> and can sometimes be a pain to track down
>> This doesn't make any sense to me - there are many selects in the
>> system and this is one of them.
>
> This was specifically requested by Stephen Boyd, and the above are
> his words verbatum
> https://lkml.org/lkml/2015/10/21/956
I am soon going to introduce a new clock driver under drivers/clk/bcm/
which is going to need some Kconfig tweaks as well, it would be good if
we reached consensus on this so Stephen can apply this.
Thanks!
--
Florian
next prev parent reply other threads:[~2015-10-22 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 19:25 [PATCH] clk: iproc: Make clocks visible options Jon Mason
2015-10-22 19:46 ` Scott Branden
2015-10-22 20:14 ` Jon Mason
2015-10-22 21:57 ` Florian Fainelli [this message]
2015-10-22 23:16 ` Scott Branden
2015-10-28 0:34 ` 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=56295BDD.4000609@broadcom.com \
--to=fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=jonmason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rjui@broadcom.com \
--cc=sboyd@codeaurora.org \
--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).