public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Kevin Hilman <khilman@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	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,
	Wei Xu <xuwei5@hisilicon.com>
Subject: Re: [PATCH] clk: Hi6220: separately build stub clock driver
Date: Fri, 4 Sep 2015 22:41:47 +0800	[thread overview]
Message-ID: <20150904144147.GA3890@leoy-linaro> (raw)
In-Reply-To: <7h7fo7pk5c.fsf@deeprootsystems.com>

On Thu, Sep 03, 2015 at 09:01:03AM -0700, Kevin Hilman wrote:
> Leo Yan <leo.yan@linaro.org> writes:
> 
> > 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>
> 
> Tested-by: Kevin Hilman <khilman@linaro.org>
> 
> I verifed that this patch on top of next-20150902  fixes the hikey boot
> failure I was seeing.

Thanks, Kevin and Stephen :)

      reply	other threads:[~2015-09-04 14:41 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
2015-09-03 16:01 ` Kevin Hilman
2015-09-04 14:41   ` Leo Yan [this message]

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=20150904144147.GA3890@leoy-linaro \
    --to=leo.yan@linaro.org \
    --cc=bintian.wang@huawei.com \
    --cc=haojian.zhuang@linaro.org \
    --cc=jorge.ramirez-ortiz@linaro.org \
    --cc=khilman@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox