On Tue, Oct 18, 2016 at 01:57:47AM +0800, ayaka wrote: > > > On 10/18/2016 12:27 AM, Krzysztof Kozlowski wrote: > >On Mon, Sep 19, 2016 at 11:48:22PM +0800, Randy Li wrote: > >>The TOPEET itop is a samsung exnynos 4412 core board, which have > >>two package versions. This patch add the support for SCP version. > >> > >>Currently supported are USB3503A HSIC, USB OTG, eMMC, rtc and > >>PMIC. The future features are in the based board. Also MFC and > >>watchdog have been enabled. > >> > >>Signed-off-by: Randy Li <ayaka@xxxxxxxxxxx> > >>--- > >> arch/arm/boot/dts/exynos4412-itop-scp-core.dtsi | 501 ++++++++++++++++++++++++ > >> 1 file changed, 501 insertions(+) > >> create mode 100644 arch/arm/boot/dts/exynos4412-itop-scp-core.dtsi > >I wanted to apply it... but then I saw a bunch of checkpatch trivial issues. > >Really, after v8? The code must compile (v6 did not compile...), there > >should be no warnings from smatch, sparse and checkpatch (only the last > >one is applicable for DTS). Unless of course checkpatch would be > >wrong... but in this case it is correct. You did not follow coding > >style: > > > >WARNING: please, no spaces at the start of a line > >#134: FILE: arch/arm/boot/dts/exynos4412-itop-scp-core.dtsi:109: > >+ devfreq = <&bus_leftbus>;$ > > > >ERROR: code indent should use tabs where possible > >#135: FILE: arch/arm/boot/dts/exynos4412-itop-scp-core.dtsi:110: > >+ status = "okay";$ > Oh, it is a copy mistake, the copy operation makes the original tab becomes > spaces. > Should I send a new version to correct them? Yes, please send new version. The DTS (code) itself looked fine, so only the checkpatch issues are remaining. BTW, why are you copying the files? Even if you have multiple trees (like product/vendor kernel and mainline) then you can easily move patches with cherry-pick, apply or am commands. Then finally just 'git format-patch -2 -v9' and 'git send-email'. Best regards, Krzysztof -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
