On 3/20/2014 4:03 AM, Scott Wood wrote:
On Sat, Jan 25, 2014 at 05:10:59PM +0530, Prabhakar Kushwaha wrote:
+ corenet-cf@18000 {
+ compatible = fsl,corenet-cf;
+ reg = 0x18000 0x1000;
+ interrupts = 16 2 1 31;
+ fsl,ccf-num-csdids =
On Wed, 2014-04-02 at 15:10 -0700, Cody P Schafer wrote:
Make the not enabled message less awful.
Signed-off-by: Cody P Schafer c...@linux.vnet.ibm.com
---
arch/powerpc/perf/hv-24x7.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/perf/hv-24x7.c
On Wed, 2014-04-02 at 21:37 +0530, Aneesh Kumar K.V wrote:
From: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
We need to handle numa pte via the slow path
Is this -stable material ? If yes how far back ?
Cheers,
Ben.
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
---
Hi Tony,
When building modules with a native le toolchain the linker will
generate R_PPC64_TOCSAVE relocations when it's safe to omit saving r2
on a plt call. This isn't helpful in the conext of a kernel module
and the kernel will fail to load those modules with an error like:
On Fri, Apr 4, 2014 at 9:11 AM, Michal Simek mon...@monstr.eu wrote:
On 04/04/2014 03:32 PM, Rob Herring wrote:
On Fri, Apr 4, 2014 at 8:22 AM, Michal Simek mon...@monstr.eu wrote:
On 04/04/2014 03:00 PM, Rob Herring wrote:
On Fri, Apr 4, 2014 at 7:16 AM, Michal Simek mon...@monstr.eu wrote:
Hi
That's not much less awful... The message gives 0 informations about
where it comes from .. what is it that couldn't obtain capabilities ?
Cody is at least using pr_fmt to give some information on what went
wrong:
[1.635040] hv-24x7: not a virtualized system, not enabling
[
Hi,
I built an allmodconfig kernel last Friday and tried inserting every module.
There were quite a few that oops because they probe ISA space.
Anton
--
Unable to handle kernel paging request for data at address 0xd80001f2
NIP [d3f3ff98] probe_chip_type+0x244/0x11d4
On Fri, 2014-04-04 at 09:18 -0700, Dave Hansen wrote:
On 04/03/2014 11:27 PM, Madhavan Srinivasan wrote:
This patch creates infrastructure to move the FAULT_AROUND_ORDER
to arch/ using Kconfig. This will enable architecture maintainers
to decide on suitable FAULT_AROUND_ORDER value based on
