Re: [PATCH] staging: tidspbridge - configure full L1 MMU range

[Felipe Contreras]

On Wed, Jan 5, 2011 at 8:20 AM, Fernando Guzman Lugo
<fernando.lugo@xxxxxx> wrote:
> Otherwise a virtual address beyond of the L1 size is used,
> the MMU hardware will look into a memory that does not belong to
> L1 translation tables. IOW; the MMU would allow to access any
> memory, configured or not.
>
> Reported-by: Felipe Contreras <felipe.contreras@xxxxxxxxx>
> Signed-off-by: Fernando Guzman Lugo <fernando.lugo@xxxxxx>
> Signed-off-by: Felipe Contreras <felipe.contreras@xxxxxxxxx>

People rarely use ' - ' in the commit summary:
% git log --oneline -1000 | grep -e ' - ' | wc -l
32

Which means about only 3%. If you do the same on
drivers/staging/tidspbridge, you'll see that the only commits that
have that are from you.

staging: tidspbridge: configure full L1 MMU range

Other than that, I think this is is a critical bugfix, and should be
applied ASAP.

Cheers.

-- 
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/