linux-kernel - Re: [PATCH] clk: Hi6220: separately build stub clock driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150904144147.GA3890@leoy-linaro>
Date:	Fri, 4 Sep 2015 22:41:47 +0800
From:	Leo Yan <leo.yan@...aro.org>
To:	Kevin Hilman <khilman@...nel.org>
Cc:	Michael Turquette <mturquette@...libre.com>,
	Stephen Boyd <sboyd@...eaurora.org>,
	Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@...aro.org>,
	Zhangfei Gao <zhangfei.gao@...aro.org>,
	Bintian Wang <bintian.wang@...wei.com>,
	Haojian Zhuang <haojian.zhuang@...aro.org>,
	linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
	Wei Xu <xuwei5@...ilicon.com>
Subject: Re: [PATCH] clk: Hi6220: separately build stub clock driver

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

Thanks, Kevin and Stephen :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/