Re: [PATCH] PCI: portdrv: fix irq initialization on FSL pcie host controller

2011-05-07 Thread Kumar Gala
On Apr 28, 2011, at 3:01 AM, Xu Lei wrote: > > Any feedback on this patch? Thanks. > > On Friday, 2011-04-22 at 15:43 +0800, Lei Xu wrote: >> Root complex ports for Freescale PCIe host controller only receive >> interrupts, so if there is no irq setting for RC, it should not return >> err

Re: [PATCH 1/2] ppc: Fix compiler warning in ptrace.c [-Wno-array-bounds]

2011-05-07 Thread Stratos Psomadakis
On 05/07/2011 06:18 PM, Andreas Schwab wrote: > Stratos Psomadakis writes: > >> +CFLAGS_ptrace.o += -DUTS_MACHINE='"$(UTS_MACHINE)"' >> -Wno-array-bounds > You need to check first whether the option is valid. > > Andreas. > I resent the patch, with $(call cc-option) to check if GCC su

[RESEND PATCH 1/2] ppc: Fix compiler warning in ptrace.c [-Wno-array-bounds]

2011-05-07 Thread Stratos Psomadakis
The trick used to bypass the thread_struct fpr array in order to access the struct fpscr, in arch/powerpc/kernel/ptrace.c, can trigger an "array subscript is above array bounds [-Werror=array-bounds]" warning. Add -Wno-array-bounds to CFLAGS_ptrace.o, in arch/powerpc/kernel/Makefile to slience thi

Re: [PATCH 1/2] ppc: Fix compiler warning in ptrace.c [-Wno-array-bounds]

2011-05-07 Thread Andreas Schwab
Stratos Psomadakis writes: > +CFLAGS_ptrace.o += -DUTS_MACHINE='"$(UTS_MACHINE)"' > -Wno-array-bounds You need to check first whether the option is valid. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "

[PATCH 1/2] ppc: Fix compiler warning in ptrace.c [-Wno-array-bounds]

2011-05-07 Thread Stratos Psomadakis
The trick used to bypass the thread_struct fpr array in order to access the struct fpscr, in arch/powerpc/kernel/ptrace.c, can trigger an "array subscript is above array bounds [-Werror=array-bounds]" warning. Add -Wno-array-bounds to CFLAGS_ptrace.o, in arch/powerpc/kernel/Makefile to slience thi

[PATCH 0/2] ppc/cleaup: Fix compiler warnings

2011-05-07 Thread Stratos Psomadakis
Fix compiler warnings in ppc code, which can lead to build failure, if CONFIG_PPC_WERROR is set (default). arch/powerpc/include/asm/pgtable-ppc64.h | 13 ++--- arch/powerpc/kernel/Makefile |2 +- 2 files changed, 7 insertions(+), 8 deletions(-) __

[PATCH 2/2] ppc64: Fix compiler warning in pgtable-ppc64.h [-Wunused-but-set-variable]

2011-05-07 Thread Stratos Psomadakis
The variable 'old' is set but not used in the wrprotect functions in arch/powerpc/include/asm/pgtable-ppc64.h, which can trigger a compiler warning. Remove the variable, since it's not used anyway. Signed-off-by: Stratos Psomadakis --- arch/powerpc/include/asm/pgtable-ppc64.h | 13 ++-

Re: [PATCH] lib: Consolidate DEBUG_STACK_USAGE option

2011-05-07 Thread Mike Frysinger
On Sat, May 7, 2011 at 01:57, Stephen Boyd wrote: > Most arches define CONFIG_DEBUG_STACK_USAGE exactly the same way. > Move it to lib/Kconfig.debug so each arch doesn't have to define > it. This obviously makes the option generic, but that's fine > because the config is already used in generic cod

Regarding P2020 in AMP mode

2011-05-07 Thread Prasanna Khanapur
Hi, I'm running P2020 in AMP mode, each core running its linux os. Ethernet 1(@25000) and Ethernet 2(@26000) assigned to Core0 are working fine. I'm facing problems with Ethernet interface(@24000) assigned to Core1, its not working. I'm using dts file which were added by : http://lists.ozlabs.org/

Re: [PATCH] lib: Consolidate DEBUG_STACK_USAGE option

2011-05-07 Thread richard -rw- weinberger
On Sat, May 7, 2011 at 7:57 AM, Stephen Boyd wrote: > Most arches define CONFIG_DEBUG_STACK_USAGE exactly the same way. > Move it to lib/Kconfig.debug so each arch doesn't have to define > it. This obviously makes the option generic, but that's fine > because the config is already used in generic

Re: [PATCH] lib: Consolidate DEBUG_STACK_USAGE option

2011-05-07 Thread David Miller
From: Stephen Boyd Date: Fri, 6 May 2011 22:57:11 -0700 > Most arches define CONFIG_DEBUG_STACK_USAGE exactly the same way. > Move it to lib/Kconfig.debug so each arch doesn't have to define > it. This obviously makes the option generic, but that's fine > because the config is already used in ge