[PATCH v3 0/4] ARM: pxa: Fix out of vmalloc space bug

[Ezequiel Garcia]

On 10 Apr 08:31 PM, Nicolas Pitre wrote:
> On Fri, 11 Apr 2014, Laurent Pinchart wrote:
> 
> > On Wednesday 09 April 2014 15:05:26 Nicolas Pitre wrote:
> > > On Wed, 9 Apr 2014, Laurent Pinchart wrote:
> > > > Hello,
> > > > 
> > > > (Resending due to a typo in an e-mail address that caused LAKML to reject
> > > > the mails. Sorry about the noise.)
> > > > 
> > > > This patch set reworks Ezequiel Garcia's previous fix [1] of an out of
> > > > vmalloc space bug on PXA2[57]x platforms caused by an attempt to map the
> > > > start of physical uncached outside of the vmalloc space.
> > > > 
> > > > This first three patches perform a couple of cleanups, and the last patch
> > > > fixes the problem. I've decided to map the memory at address 0xfe000000 to
> > > > minimize changes to the code, but this causes a bit of fragmentation of
> > > > vmalloc space. I could map it to the very end of vmalloc space
> > > > (0xfef00000)
> > > > instead if preferred, which would involve replacing a mov by an ldr in
> > > > pxa2[57]x_finish_suspend and pm_enter_standby_start.
> > > > 
> > > > I've tested the patch set on a PXA270-based system.
> > > 
> > > For those patches:
> > > 
> > > Acked-by: Nicolas Pitre <nico at linaro.org>
> > 
> > Thank you.
> > 
> > MAINTAINERS lists three maintainers for the PXA architecture, and two git 
> > trees that seem to be either dead or even deleted. Who picks up patches for 
> > PXA ? Should I send a pull request ?
> 
> If no one else answers, then just send a pull request to the ARM-SOC 
> team (arm at kernel.org) and CC the linux-arm-kernel mailing list.
> 

What ever happened to this?
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com