linux-kernel - Re: [PATCH 0/3] ARM: dts: Use IOPAD pinmux for IGEP boards

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

Message-ID: <20151020162608.GI3078@atomide.com>
Date:	Tue, 20 Oct 2015 09:26:09 -0700
From:	Tony Lindgren <tony@...mide.com>
To:	Javier Martinez Canillas <javier@....samsung.com>
Cc:	linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/3] ARM: dts: Use IOPAD pinmux for IGEP boards

* Javier Martinez Canillas <javier@....samsung.com> [151019 08:39]:
> Hello,
> 
> This series use the IOPAD pinmux macros for the remaining IGEP boards that
> still used the register offset instead of the physical address using these
> macros so the DTS matches what is in the Technical Reference Manual.
> 
> The changes are only cosmetic since they make the DTS easier to read but
> does not change functionality. I built tested and compared the binary DTB
> MD5 checksum and both matches before and after the series applied:
> 
> Before
> 
> d7a56205bdc54365d49d9a90dfe3fafb  am335x-base0033.dtb
> fa272fcdee65d7bf4c03bd5a6c5ec4fd  omap3-igep0020.dtb
> ba65bf74d8c6ea8e7bd8face17179e6e  omap3-igep0020-rev-f.dtb
> 
> After
> 
> d7a56205bdc54365d49d9a90dfe3fafb  am335x-base0033.dtb
> fa272fcdee65d7bf4c03bd5a6c5ec4fd  omap3-igep0020.dtb
> ba65bf74d8c6ea8e7bd8face17179e6e  omap3-igep0020-rev-f.dtb

Good idea to test the dtb checksums :)

Applying all into omap-for-v4.4/dt thanks.

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