public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: linux-kernel@vger.kernel.org, mturquette@baylibre.com,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH] Make Common clock framework a menuconfig to ease disabling it all
Date: Wed, 5 Jul 2017 14:15:18 -0700	[thread overview]
Message-ID: <20170705211518.GU22780@codeaurora.org> (raw)
In-Reply-To: <1499011768-8046-1-git-send-email-vincent.legoll@gmail.com>

On 07/02, Vincent Legoll wrote:
> No need to get into the submenu to disable all common clock framework
> -related config entries
> 
> Signed-off-by: Vincent Legoll <vincent.legoll@gmail.com>
> ---
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 36cfea3..a1b174c 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -19,9 +19,12 @@ config COMMON_CLK
>  	  Architectures utilizing the common struct clk should select
>  	  this option.
>  
> -menu "Common Clock Framework"
> +menuconfig COMMON_CLK_FRAMEWORK
> +	tristate "Common Clock Framework"
>  	depends on COMMON_CLK

Wouldn't this put the clk drivers inside the drivers menu? Which
is already quite large right now. Plus this makes common clk
tristate which so far we haven't supported. No thanks.

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

  parent reply	other threads:[~2017-07-05 21:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-02 16:09 [PATCH] Make Common clock framework a menuconfig to ease disabling it all Vincent Legoll
2017-07-04 23:43 ` kbuild test robot
2017-07-04 23:46 ` kbuild test robot
2017-07-05 21:15 ` Stephen Boyd [this message]
2017-07-06  7:25   ` Vincent Legoll

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=20170705211518.GU22780@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=vincent.legoll@gmail.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