From: Stephen Boyd <sboyd@codeaurora.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Bintian Wang <bintian.wang@huawei.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Kevin Hilman <khilman@kernel.org>, Wei Xu <xuwei5@hisilicon.com>
Subject: Re: [PATCH] clk: Hi6220: separately build stub clock driver
Date: Wed, 2 Sep 2015 17:09:34 -0700 [thread overview]
Message-ID: <20150903000934.GD15099@codeaurora.org> (raw)
In-Reply-To: <1441162667-25532-1-git-send-email-leo.yan@linaro.org>
On 09/02, Leo Yan wrote:
> The previous code, kernel builds Hi6220's common clock driver and stub
> clock driver together. Stub clock driver has introduced the dependency
> with CONFIG_MAILBOX, so kernel will not build Hi6220's common clock
> driver due ARM64's defconfig have not enabled CONFIG_MAILBOX by default.
>
> So separately build stub clock driver and common clock driver for
> Hi6220; and only let stub clock driver has the dependency with
> CONFIG_MAILBOX.
>
> Signed-off-by: Leo Yan <leo.yan@linaro.org>
> ---
I had to read it a couple times, but it makes sense.
Applied to clk-fixes
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-09-03 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 2:57 [PATCH] clk: Hi6220: separately build stub clock driver Leo Yan
2015-09-03 0:09 ` Stephen Boyd [this message]
2015-09-03 16:01 ` Kevin Hilman
2015-09-04 14:41 ` Leo Yan
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=20150903000934.GD15099@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bintian.wang@huawei.com \
--cc=haojian.zhuang@linaro.org \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=khilman@kernel.org \
--cc=leo.yan@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=xuwei5@hisilicon.com \
--cc=zhangfei.gao@linaro.org \
/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.