[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD3Xx4Jf5ACBKe-KvGRD=myHKrJ+K_P0vBrtrmfgh+1zNM4hug@mail.gmail.com>
Date: Tue, 10 Mar 2015 16:32:29 +0100
From: Valentin Rothberg <valentinrothberg@...il.com>
To: Sylwester Nawrocki <s.nawrocki@...sung.com>,
Tomasz Figa <tomasz.figa@...il.com>,
Mike Turquette <mturquette@...aro.org>,
Stephen Boyd <sboyd@...eaurora.org>,
Kukjin Kim <kgene@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Chanwoo Choi <cw00.choi@...sung.com>,
Inki Dae <inki.dae@...sung.com>, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
Andreas Ruprecht <rupran@...server.de>,
hengelein Stefan <stefan.hengelein@....de>,
Paul Bolle <pebolle@...cali.nl>
Subject: ARCH_EXYNOS5433 missing in Kconfig
Hi Chanwoo,
your commit 96bd6224f07b ("clk: samsung: exynos5433: Add clocks using
common clock framework") is included in today's linux-next tree (i.e.,
next-20150310).
This patch conditionally compiles clk-exynos5433.c depending on the
Kconfig option ARCH_EXYNOS5433. However, this option is not defined
in Kconfig, so that the driver cannot be compiled at the current
state:
+obj-$(CONFIG_ARCH_EXYNOS5433) += clk-exynos5433.o
Is there a patch queued somewhere that adds this Kconfig symbol? I
detected the issue by running undertaker-checkpatch from the
Undertaker tool suite (undertaker.cs.fau.de). There is also a tool in
the git tree that can detect such issues (i.e.,
scripts/checkkconfigsymbols.py).
Kind regards,
Valentin
--
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/
Powered by blists - more mailing lists