On 08/22/2015 05:12 AM, Michael Ellerman wrote:
When I merged the OPAL support for the powernv LEDS driver I missed a
hunk.
This is slightly modified from the original patch, as the original added
code to opal-api.h which is not in the skiboot version, which is
discouraged.
Yeah. I should
On 08/22/2015 05:10 AM, Michael Ellerman wrote:
On Fri, 2015-08-21 at 14:29 +0530, Vasant Hegde wrote:
On 08/21/2015 01:55 PM, Stephen Rothwell wrote:
Hi all,
After merging the nvdimm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
Stephen,
Thanks for reporting! I
show_interrupts() expects the irq_chip name to be max 8 characters
otherwise everything get misaligned
# cat /proc/interrupts
CPU0
17: 0 CPM PIC 0 Level error
19: 0 MPC8XX SIU 15 Level tbint
20: 90 CPM PIC 4 Level cpm_uart
38:
rh_alloc() returns (unsigned long)-ERRxx on error, which may
result in overwriting memory outside the MURAM AREA.
Signed-off-by: Christophe Leroy christophe.le...@c-s.fr
---
arch/powerpc/sysdev/cpm_common.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Fri, 2015-08-21 at 14:29 +0530, Vasant Hegde wrote:
On 08/21/2015 01:55 PM, Stephen Rothwell wrote:
Hi all,
After merging the nvdimm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
Stephen,
Thanks for reporting! I checked powerpc tree.. This is because of
When I merged the OPAL support for the powernv LEDS driver I missed a
hunk.
This is slightly modified from the original patch, as the original added
code to opal-api.h which is not in the skiboot version, which is
discouraged.
Instead those values are moved into the driver, which is the only
* Kevin Hao haoke...@gmail.com wrote:
On Fri, Aug 21, 2015 at 08:28:26AM +0200, Ingo Molnar wrote:
* Kevin Hao haoke...@gmail.com wrote:
These are used to define a static_key_{true,false} array.
Signed-off-by: Kevin Hao haoke...@gmail.com
---
include/linux/jump_label.h
Current is using !flags, and we are going to use
IORESOURCE_DISABLED instead of clearing resource flags.
Let's convert all !flags to helper function resource_disabled().
resource_disabled will check !flags and IORESOURCE_DISABLED both.
Cc: linux-al...@vger.kernel.org
Cc:
On Fri, Aug 21, 2015 at 08:28:26AM +0200, Ingo Molnar wrote:
* Kevin Hao haoke...@gmail.com wrote:
These are used to define a static_key_{true,false} array.
Signed-off-by: Kevin Hao haoke...@gmail.com
---
include/linux/jump_label.h | 6 ++
1 file changed, 6 insertions(+)
On Fri, Aug 21, 2015 at 08:40:59AM +0200, Ingo Molnar wrote:
Please also Cc: peterz and me to the next submission of the series - static
key
(and jump label) changes go through the locking tree normally, and there's a
number of changes pending already for v4.3:
Sure.
Thanks,
Kevin
There are powerpc generic version and x86 local version for
skip_ioresource_align().
Move the powerpc version to setup-bus.c, and kill x86 local version.
Also kill dummy version in microblaze.
Cc: Michal Simek mon...@monstr.eu
Cc: Paul Mackerras pau...@samba.org
Cc: Michael Ellerman
On Wed, 2015-22-07 at 05:50:51 UTC, Samuel Mendoza-Jonas wrote:
On powernv secondary cpus are returned to OPAL, and will then enter
the target kernel in big-endian. However if it is set the HILE bit
will persist, causing the first exception in the target kernel to be
delivered in litte-endian
Hi all,
After merging the nvdimm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/leds/leds-powernv.c:30:3: error: 'OPAL_SLOT_LED_TYPE_ID' undeclared
here (not in a function)
{OPAL_SLOT_LED_TYPE_ID, POWERNV_LED_TYPE_IDENTIFY},
^
On Fri, 2015-31-07 at 09:29:50 UTC, Laurent Dufour wrote:
This patch fixes several endianness issues detected when running the HVSI
driver in little endian mode.
These issues are raised in little endian mode because the data exchanged in
memory between the kernel and the hypervisor has to be
Acked-by: Ian Munsie imun...@au1.ibm.com
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
On 08/21/2015 01:55 PM, Stephen Rothwell wrote:
Hi all,
After merging the nvdimm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
Stephen,
Thanks for reporting! I checked powerpc tree.. This is because of commit
8a8d9181 in powerpc tree.. Basically Michael missed one
cxl_reset currently PERSTs the slot, and then repeatedly tries to
read MMIO space in order to kick off EEH.
There are 2 problems with this: it's unnecessary, and it's racy.
It's unnecessary because the PERST will bring down the PHB link.
That will be picked up by the CAPP, which will send out an
On Wed, 2015-22-07 at 05:50:50 UTC, Samuel Mendoza-Jonas wrote:
If the target kernel does not inlcude the FIXUP_ENDIAN check, coming
from a different-endian kernel will cause the target kernel to panic.
All ppc64 kernels can handle starting in big-endian mode, so return to
big-endian before
For device resource PREF bit setting under bridge 64-bit pref resource,
we need to make sure only set PREF for 64bit resource, so set
IORESOUCE_MEM_64 for 64bit resource during of device resource flags
parsing.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261
Link:
* Kevin Hao haoke...@gmail.com wrote:
These are used to define a static_key_{true,false} array.
Signed-off-by: Kevin Hao haoke...@gmail.com
---
include/linux/jump_label.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/linux/jump_label.h b/include/linux/jump_label.h
20 matches
Mail list logo
