linux-kernel - clk: hisilicon: ARCH_HIP04 and ARCH

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-next>] [day] [month] [year] [list]

Message-ID: <1403167807.23136.31.camel@x220>
Date:	Thu, 19 Jun 2014 10:50:07 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Mike Turquette <mturquette@...aro.org>,
	Haojian Zhuang <haojian.zhuang@...aro.org>,
	Zhangfei Gao <zhangfei.gao@...aro.org>,
	Haifeng Yan <haifeng.yan@...aro.org>
Cc:	linux-kernel@...r.kernel.org
Subject: clk: hisilicon: ARCH_HIP04 and ARCH_HIX5HD2?

0) Commit d3e6573c48f4 ("clk: hip04: add clock driver") was included in
v3.15. That clock driver is built only if CONFIG_ARCH_HIP04 is set.

And commit 5efaf09021a5 ("clk: hisi: add clk-hix5hd2.c") was included in
v3.16-rc1. And that driver is built only if CONFIG_ARCH_HIX5HD2 is set.

1) Neither the symbol ARCH_HIP04 nor the symbol ARCH_HIX5HD2 is part of
v3.16-rc1. These symbols are also not part of next-20140619. I assume
that both are pending somewhere. Is that correct?

2) It would probably be nice if these drivers got some (automatic) build
coverage until those symbols enter the tree. I don't know how that could
be achieved.

Paul Bolle

--
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/