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]
Date:	Wed, 02 Apr 2014 13:14:41 +0300
From:	Taras Kondratiuk <taras.kondratiuk@...aro.org>
To:	Tony Lindgren <tony@...mide.com>
CC:	Patch Tracking <patches@...aro.org>,
	Linaro Networking <linaro-networking@...aro.org>,
	Linaro Kernel <linaro-kernel@...ts.linaro.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	open list <linux-kernel@...r.kernel.org>,
	Victor Kamensky <victor.kamensky@...aro.org>
Subject: Re: [PATCH 0/4] ARM: OMAP: raw read and write endian fix

On 03/26/2014 12:35 PM, Taras Kondratiuk wrote:
> On 01/08/2014 02:39 AM, Tony Lindgren wrote:
>> * Taras Kondratiuk <taras.kondratiuk@...aro.org> [131223 10:20]:
>>> On 23 December 2013 20:10, Taras Kondratiuk <taras.kondratiuk@...aro.org> wrote:
>>>> This series does trivial replacement of __raw_xxx functions with xxx_relaxed
>>>> endian-neutral variants in 'mach-omap2' and 'plat-omap' directories.
>>>> Some code here most probably won't be used in BE mode (like debug-leds for
>>>> OMAP1 boards), but changes are made anyway to remove __raw_xxx() functions
>>>> completely and simplify future grep'ing for new __raw_xxx() entries.
>>
>> Sorry for the delay on these, applying into omap-for-v3.14/be.
>> These are trivial, and it's actually nice that you left out the
>> assembly related changes as those should be acked by the PM
>> people in case there are some issues dealing with the ROM code
>> etc.
> 
> Hi Tony,
> 
> It seems omap-for-v3.14/be didn't get into 3.14-rc8.
> Is there any issue with them?

This series conflicts now with clock changes which got into 3.14.
Resolution is trivial - just skip conflicting changes.
omap2_clk_{real,writel} already uses {readl,writel}_relaxed inside.
Do I need to push an updated series?

-- 
Taras Kondratiuk
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ