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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 7 Feb 2013 18:35:43 +0400
From:	Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To:	Michal Simek <monstr@...str.eu>
CC:	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Grant Likely <grant.likely@...retlab.ca>,
	Arnd Bergmann <arnd@...db.de>,
	Vineet Gupta <Vineet.Gupta1@...opsys.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"Geert Uytterhoeven" <geert@...ux-m68k.org>,
	<dahinds@...rs.sourceforge.net>, <gsmecher@...eespeedlogic.com>
Subject: Re: [PATCH] drivers/block/xsysace - replace in(out)_8/in(out)_be16/in(out)_le16
 with generic iowrite(read)8/16(be)

On 02/07/2013 06:31 PM, Michal Simek wrote:
> The origin patch (after some microblaze ioread/iowrite fixes) works ok,
> These additional changes is breaking sysace on microblaze big endian
> ml505 16bit mode.
> 8bit mode just works
>
> Also I have looked at our tree and I see that the mainline kernel misses
> one patch which was sent by Graeme Smecher and it was also Acked-by Grant.
> It is called "Fix device name assignment for SystemACE (from "xs`" to "xsa")."
> Let me resend it too.
>
> Alexey: Can you please confirm that on your arc platform you see broken CF
> partitions name?
>
> Thanks,
> Michal
>

Indeed I had it and fixed myself)
I didn't know about this fix so I've just sent another fix for it - 
https://patchwork.kernel.org/patch/2110811/

Anyways good to know now it is fixed.

Thanks,
Alexey
--
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