From: Stewart Smith <stewart@linux•vnet.ibm.com>
To: Vasant Hegde <hegdevasant@linux•vnet.ibm.com>, mpe@ellerman•id.au
Cc: linuxppc-dev@lists•ozlabs.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls
Date: Thu, 19 Feb 2015 11:43:57 +1100 [thread overview]
Message-ID: <m38ufuhgs2.fsf@oc8180480414.ibm.com> (raw)
In-Reply-To: <54E445CC.9090304@linux.vnet.ibm.com>
Vasant Hegde <hegdevasant@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. :)
prev parent reply other threads:[~2015-02-19 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 0:03 [PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls Stewart Smith
2015-02-18 0:03 ` [PATCH 1/3] powerpc/powernv: only register log if OPAL supports doing so Stewart Smith
2015-02-18 0:03 ` [PATCH 2/3] powerpc/powernv: only call OPAL_ELOG_RESEND if firmware supports it Stewart Smith
2015-02-18 0:03 ` [PATCH 3/3] powerpc/powernv: only call OPAL_RESEND_DUMP " Stewart Smith
2015-02-18 7:57 ` [PATCH 0/3] powerpc/powernv: Correctly detect optional OPAL calls Vasant Hegde
2015-02-19 0:43 ` Stewart Smith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m38ufuhgs2.fsf@oc8180480414.ibm.com \
--to=stewart@linux$(echo .)vnet.ibm.com \
--cc=hegdevasant@linux$(echo .)vnet.ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox