On Friday 26 October 2012 10:11 PM, Tony Lindgren wrote:
* Paul Walmsleyp...@pwsan.com [121025 22:05]:
It also breaks an OMAP3+4 config:
Fix below.
Thanks, I'd like to pull this fix in too along with the
others.
Thanks Paul and Tony for taking care of this issue.
I am sorry about the
* Paul Walmsley p...@pwsan.com [121025 18:50]:
Hi Afzal
On Mon, 8 Oct 2012, Afzal Mohammed wrote:
platform data now contains a field to indicate whether
soc belongs to omap34xx family, use it instead of
cpu_is_* check.
This helps in removing dependency of platform specific
* Paul Walmsley p...@pwsan.com [121025 22:05]:
On Fri, 26 Oct 2012, Paul Walmsley wrote:
On Mon, 8 Oct 2012, Afzal Mohammed wrote:
platform data now contains a field to indicate whether
soc belongs to omap34xx family, use it instead of
cpu_is_* check.
This helps in removing
Hi Afzal
On Mon, 8 Oct 2012, Afzal Mohammed wrote:
platform data now contains a field to indicate whether
soc belongs to omap34xx family, use it instead of
cpu_is_* check.
This helps in removing dependency of platform specific
header file - cpu.h
Signed-off-by: Afzal Mohammed
On Fri, 26 Oct 2012, Paul Walmsley wrote:
On Mon, 8 Oct 2012, Afzal Mohammed wrote:
platform data now contains a field to indicate whether
soc belongs to omap34xx family, use it instead of
cpu_is_* check.
This helps in removing dependency of platform specific
header file - cpu.h
platform data now contains a field to indicate whether
soc belongs to omap34xx family, use it instead of
cpu_is_* check.
This helps in removing dependency of platform specific
header file - cpu.h
Signed-off-by: Afzal Mohammed af...@ti.com
---
drivers/mtd/onenand/omap2.c | 7 ---
1 file
