linux-kernel - Re: [PATCH] ARM: OMAP4: sleep: byteswap data for big-endian

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

Message-ID: <20140213174724.GB27022@atomide.com>
Date:	Thu, 13 Feb 2014 09:47:25 -0800
From:	Tony Lindgren <tony@...mide.com>
To:	Santosh Shilimkar <santosh.shilimkar@...com>
Cc:	Nishanth Menon <nm@...com>,
	Linaro Kernel <linaro-kernel@...ts.linaro.org>,
	Russell King <linux@....linux.org.uk>,
	Patch Tracking <patches@...aro.org>,
	Taras Kondratiuk <taras.kondratiuk@...aro.org>,
	Victor Kamensky <victor.kamensky@...aro.org>,
	open list <linux-kernel@...r.kernel.org>,
	Tero Kristo <t-kristo@...com>,
	Linaro Networking <linaro-networking@...aro.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] ARM: OMAP4: sleep: byteswap data for big-endian

* Santosh Shilimkar <santosh.shilimkar@...com> [140114 15:46]:
> On Tuesday 14 January 2014 04:13 PM, Nishanth Menon wrote:
> 
> I haven't looked at patch myself but as you pointed out if it adds
> dead code and makes the code un-readable then probably that something
> we shouldn't merge.

Yeah it seems the assembly parts should be done in more generic
way using macros so the same setup can then be used for other
SoCs. For the other trivial changes, let's try to get them merged
to shrink down the patchset.

Regards,

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/