linux-kernel - Re: [PATCH v2 00/23] ARM: LPC32xx specific updates for next

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:	Fri, 15 Jun 2012 14:37:45 +0200
From:	Roland Stigge <stigge@...com.de>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Alexandre Pereira da Silva <aletes.xgr@...il.com>, arm@...nel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	kevin.wells@....com, srinivas.bakki@....com
Subject: Re: [PATCH v2 00/23] ARM: LPC32xx specific updates for next

Hi,

On 06/15/2012 02:12 PM, Alexandre Pereira da Silva wrote:
> On Fri, Jun 15, 2012 at 9:07 AM, Arnd Bergmann <arnd@...db.de> wrote:
>> It all looks good from my point of view, so I think we can pull it
>> for 3.6 if no other comments come.
> 
> Arn,
> 
> Please exclude "ARM: LPC32xx: Remove duplicate usb host clock init".
> It's causing problems in some LPC32XX boards.

Right - it would break USB e.g. on the EA3250 board since USB would work
only if the bootloader already did some initialization which is silently
done by PHY3250 where we didn't recognize the problem.

So please just take patches 01..22 from the lpc32xx-next branch.

I just removed patch 23 from git.antcom.de, so you can easily just pull
the branch.

Further, as Russell already pointed out, the DMA API will probably
change, but I expect that we will quickly adjust to it so no need to
worry about that.

Thanks,

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