From: Stewart Smith <stewart@linux•vnet.ibm.com>
To: Mukesh Ojha <mukesh02@linux•vnet.ibm.com>, linuxppc-dev@lists•ozlabs.org
Cc: Mukesh Ojha <mukesh02@linux•vnet.ibm.com>
Subject: Re: [PATCH 1/2] powerpc/powernv/opal-dump : Handles opal_dump_info properly
Date: Wed, 15 Feb 2017 16:04:09 +1100 [thread overview]
Message-ID: <877f4s9h9y.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1480583289-6380-1-git-send-email-mukesh02@linux.vnet.ibm.com>
Mukesh Ojha <mukesh02@linux•vnet.ibm.com> writes:
> Moves the return value check of 'opal_dump_info' to a proper place which
> was previously unnecessarily filling all the dump info even on failure.
>
> Signed-off-by: Mukesh Ojha <mukesh02@linux•vnet.ibm.com>
> ---
> arch/powerpc/platforms/powernv/opal-dump.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Acked-by: Stewart Smith <stewart@linux•vnet.ibm.com>
--
Stewart Smith
OPAL Architect, IBM.
prev parent reply other threads:[~2017-02-15 5:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 9:08 [PATCH 1/2] powerpc/powernv/opal-dump : Handles opal_dump_info properly Mukesh Ojha
2016-12-01 9:08 ` [PATCH 2/2] powerpc/powernv/opal-dump : Use IRQ_HANDLED instead of numbers in interrupt handler Mukesh Ojha
2017-02-15 3:18 ` Jeremy Kerr
2017-02-15 10:27 ` Mukesh Ojha
2017-02-16 2:40 ` Jeremy Kerr
2017-02-20 13:19 ` Mukesh Ojha
2017-02-27 0:16 ` Jeremy Kerr
2017-02-15 5:08 ` Stewart Smith
2017-02-15 6:18 ` Mukesh Ojha
2016-12-06 6:37 ` [PATCH 1/2] powerpc/powernv/opal-dump : Handles opal_dump_info properly Mukesh Ojha
2017-02-13 6:32 ` Mukesh Ojha
2017-02-15 3:18 ` Jeremy Kerr
2017-02-15 5:04 ` 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=877f4s9h9y.fsf@linux.vnet.ibm.com \
--to=stewart@linux$(echo .)vnet.ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mukesh02@linux$(echo .)vnet.ibm.com \
/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