If OPAL firmware is called with an invalid token, that is, one that the current running firmware does not support, it dumps an error into its log. For three calls we were making in Linux, we were not adequately checking that the current firmware supported them, so could get this warning spuriously.
Stewart Smith (3): powerpc/powernv: only register log if OPAL supports doing so powerpc/powernv: only call OPAL_ELOG_RESEND if firmware supports it powerpc/powernv: only call OPAL_RESEND_DUMP if firmware supports it arch/powerpc/platforms/powernv/opal-dump.c | 3 ++- arch/powerpc/platforms/powernv/opal-elog.c | 3 ++- arch/powerpc/platforms/powernv/opal.c | 6 +++++- 3 files changed, 9 insertions(+), 3 deletions(-) -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
