On Fri, 2014-11-21 at 17:48 +0100, Robert Jarzmik wrote:
> Paul Bolle writes:
> > Your commit 03ec7fe70c5c ("arm: pxa: add pxa27x device-tree support") is
> > included in today's linux-next (ie, next-20141121). It adds a select
> > statement for CPU_PXA27x. But there's no Kconfig symbol
Paul Bolle writes:
> Robert,
>
> Your commit 03ec7fe70c5c ("arm: pxa: add pxa27x device-tree support") is
> included in today's linux-next (ie, next-20141121). It adds a select
> statement for CPU_PXA27x. But there's no Kconfig symbol CPU_PXA27x.
Ah yes, you're perfectly right, CPU_PXA27x was
Robert,
Your commit 03ec7fe70c5c ("arm: pxa: add pxa27x device-tree support") is
included in today's linux-next (ie, next-20141121). It adds a select
statement for CPU_PXA27x. But there's no Kconfig symbol CPU_PXA27x.
Why is that select needed? For what it's worth: __cpu_is_pxa27x()
compiles to
Robert,
Your commit 03ec7fe70c5c (arm: pxa: add pxa27x device-tree support) is
included in today's linux-next (ie, next-20141121). It adds a select
statement for CPU_PXA27x. But there's no Kconfig symbol CPU_PXA27x.
Why is that select needed? For what it's worth: __cpu_is_pxa27x()
compiles to
Paul Bolle pebo...@tiscali.nl writes:
Robert,
Your commit 03ec7fe70c5c (arm: pxa: add pxa27x device-tree support) is
included in today's linux-next (ie, next-20141121). It adds a select
statement for CPU_PXA27x. But there's no Kconfig symbol CPU_PXA27x.
Ah yes, you're perfectly right,
On Fri, 2014-11-21 at 17:48 +0100, Robert Jarzmik wrote:
Paul Bolle pebo...@tiscali.nl writes:
Your commit 03ec7fe70c5c (arm: pxa: add pxa27x device-tree support) is
included in today's linux-next (ie, next-20141121). It adds a select
statement for CPU_PXA27x. But there's no Kconfig symbol
6 matches
Mail list logo
