[Skiboot] [PATCH RFC v2 03/12] opal-prd: allow different chips for occ control actions

Vasant Hegde hegdevasant at linux.vnet.ibm.com
Fri May 26 19:51:28 AEST 2017

On 05/26/2017 08:24 AM, Jeremy Kerr wrote:
> The `occ reset` and `occ error` actions can both take a chip id
> argument, but we're currently just using zero. This change changes the
> control message format to pass the chip ID from the control process to
> the opal-prd daemon.
> Signed-off-by: Jeremy Kerr <jk at ozlabs.org>

Looks good. Working fine on P9.

Reviewed-by: Vasant Hegde <hegdevasant at linux.vnet.ibm.com>


More information about the Skiboot mailing list