| 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
| ||
|
Date: Tue, 11 Mar 2014 11:20:27 +0000 From: Lee Jones <lee.jones@...aro.org> To: Maxime Coquelin <maxime.coquelin@...com> Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, srinivas.kandagatla@...com Subject: Re: [PATCH 2/3] ARM: STi: stih416-b2020: Explicitly include STiH416 Pinctrl bindings > >At the moment we're relying on inheriting them from DTSI files which > >we're including Ideally we should be specifying these for ourselves. > > > >Signed-off-by: Lee Jones <lee.jones@...aro.org> > >--- > > arch/arm/boot/dts/stih416-b2020-revE.dts | 1 + > > 1 file changed, 1 insertion(+) > > > >diff --git a/arch/arm/boot/dts/stih416-b2020-revE.dts b/arch/arm/boot/dts/stih416-b2020-revE.dts > >index bcb9d00..4168b019 100644 > >--- a/arch/arm/boot/dts/stih416-b2020-revE.dts > >+++ b/arch/arm/boot/dts/stih416-b2020-revE.dts > >@@ -8,6 +8,7 @@ > > */ > > /dts-v1/; > > #include "stih416.dtsi" > >+#include "stih416-pinctrl.dtsi" > Isn't this file already included in stih416.dtsi? It is, but it's being inherited. I'm unsure if the DT rules are different, but in *.c files #includes should be added explicitly in the file they are used. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- 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