From: Matthias Brugger <matthias.bgg@gmail.com>
To: Jean Delvare <jdelvare@suse.de>,
linux-clk@vger.kernel.org, linux-mediatek@lists.infradead.org
Cc: Shunli Wang <shunli.wang@mediatek.com>,
James Liao <jamesjj.liao@mediatek.com>,
Erin Lo <erin.lo@mediatek.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH] clk: mediatek: Add hardware dependency
Date: Fri, 14 Oct 2016 19:43:29 +0200 [thread overview]
Message-ID: <d698e9d7-cb57-ae75-e26a-c0dc1c5fce1b@gmail.com> (raw)
In-Reply-To: <20161014144413.1f0225b5@endymion>
On 10/14/2016 02:44 PM, Jean Delvare wrote:
> Only propose the mediatek clock drivers on this platform, unless
> build-testing.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Cc: Shunli Wang <shunli.wang@mediatek.com>
> Cc: James Liao <jamesjj.liao@mediatek.com>
> Cc: Erin Lo <erin.lo@mediatek.com>
> Cc: Matthias Brugger <matthias.bgg@gmail.com>
> Cc: Stephen Boyd <sboyd@codeaurora.org>
> Cc: Michael Turquette <mturquette@baylibre.com>
> ---
> drivers/clk/mediatek/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- linux-4.9-rc0.orig/drivers/clk/mediatek/Kconfig 2016-10-13 11:39:40.416106971 +0200
> +++ linux-4.9-rc0/drivers/clk/mediatek/Kconfig 2016-10-14 14:37:48.319588483 +0200
> @@ -8,6 +8,7 @@ config COMMON_CLK_MEDIATEK
>
> config COMMON_CLK_MT8135
> bool "Clock driver for Mediatek MT8135"
> + depends on ARCH_MEDIATEK || COMPILE_TEST
> select COMMON_CLK_MEDIATEK
> default ARCH_MEDIATEK
> ---help---
> @@ -15,6 +16,7 @@ config COMMON_CLK_MT8135
>
> config COMMON_CLK_MT8173
> bool "Clock driver for Mediatek MT8173"
> + depends on ARCH_MEDIATEK || COMPILE_TEST
> select COMMON_CLK_MEDIATEK
> default ARCH_MEDIATEK
> ---help---
>
>
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
next prev parent reply other threads:[~2016-10-14 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 12:44 [PATCH] clk: mediatek: Add hardware dependency Jean Delvare
2016-10-14 17:43 ` Matthias Brugger [this message]
2016-10-17 22:22 ` 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=d698e9d7-cb57-ae75-e26a-c0dc1c5fce1b@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=erin.lo@mediatek.com \
--cc=jamesjj.liao@mediatek.com \
--cc=jdelvare@suse.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=shunli.wang@mediatek.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.