Re: [PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls
Vasant Hegde writes: > On 02/18/2015 05:33 AM, Stewart Smith wrote: >> This series fixes three possible warnings that OPAL firmware would emit >> when booting on hardware/simulator that didn't support certain functionality. >> >> The correct thing for Linux to do is to detect firmware capability >> by using the OPAL_CHECK_TOKEN call or examining device tree. In the case >> of these three warnings, it was OPAL_CHECK_TOKEN. > > Stewart, > Sorry.. I couldn't makeout any difference between this patchset and earlier > patchset which I had Acked except the update in cover page... (sub: Silence > "OPAL called with invalid token" errors ). > > Did I miss anything ? You missed that I forgot I'd sent the patchset. :) -- 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/
Re: [PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls
Vasant Hegde hegdevas...@linux.vnet.ibm.com writes: On 02/18/2015 05:33 AM, Stewart Smith wrote: This series fixes three possible warnings that OPAL firmware would emit when booting on hardware/simulator that didn't support certain functionality. The correct thing for Linux to do is to detect firmware capability by using the OPAL_CHECK_TOKEN call or examining device tree. In the case of these three warnings, it was OPAL_CHECK_TOKEN. Stewart, Sorry.. I couldn't makeout any difference between this patchset and earlier patchset which I had Acked except the update in cover page... (sub: Silence OPAL called with invalid token errors ). Did I miss anything ? You missed that I forgot I'd sent the patchset. :) -- 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/
Re: [PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls
On 02/18/2015 05:33 AM, Stewart Smith wrote: > This series fixes three possible warnings that OPAL firmware would emit > when booting on hardware/simulator that didn't support certain functionality. > > The correct thing for Linux to do is to detect firmware capability > by using the OPAL_CHECK_TOKEN call or examining device tree. In the case > of these three warnings, it was OPAL_CHECK_TOKEN. Stewart, Sorry.. I couldn't makeout any difference between this patchset and earlier patchset which I had Acked except the update in cover page... (sub: Silence "OPAL called with invalid token" errors ). Did I miss anything ? -Vasant -- 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/
[PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls
This series fixes three possible warnings that OPAL firmware would emit when booting on hardware/simulator that didn't support certain functionality. The correct thing for Linux to do is to detect firmware capability by using the OPAL_CHECK_TOKEN call or examining device tree. In the case of these three warnings, it was OPAL_CHECK_TOKEN. 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/
[PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls
This series fixes three possible warnings that OPAL firmware would emit when booting on hardware/simulator that didn't support certain functionality. The correct thing for Linux to do is to detect firmware capability by using the OPAL_CHECK_TOKEN call or examining device tree. In the case of these three warnings, it was OPAL_CHECK_TOKEN. 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/
Re: [PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls
On 02/18/2015 05:33 AM, Stewart Smith wrote: This series fixes three possible warnings that OPAL firmware would emit when booting on hardware/simulator that didn't support certain functionality. The correct thing for Linux to do is to detect firmware capability by using the OPAL_CHECK_TOKEN call or examining device tree. In the case of these three warnings, it was OPAL_CHECK_TOKEN. Stewart, Sorry.. I couldn't makeout any difference between this patchset and earlier patchset which I had Acked except the update in cover page... (sub: Silence OPAL called with invalid token errors ). Did I miss anything ? -Vasant -- 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/
