linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, linuxppc-dev@lists.ozlabs.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Alistair Popple <alistair@popple.id.au>,
	Sam Bobroff <sbobroff@linux.ibm.com>,
	Piotr Jaroszynski <pjaroszynski@nvidia.com>,
	Oliver O'Halloran <oohall@gmail.com>,
	Reza Arbab <arbab@linux.ibm.com>
Subject: Re: [kernel] powerpc/powernv/eeh/npu: Fix uninitialized variables in opal_pci_eeh_freeze_status
Date: Mon, 24 Dec 2018 00:28:23 +1100 (AEDT)	[thread overview]
Message-ID: <43N38m0TdCz9sNk@ozlabs.org> (raw)
In-Reply-To: <20181119042517.45075-1-aik@ozlabs.ru>

On Mon, 2018-11-19 at 04:25:17 UTC, Alexey Kardashevskiy wrote:
> The current implementation of the OPAL_PCI_EEH_FREEZE_STATUS call in
> skiboot's NPU driver does not touch the pci_error_type parameter so
> it might have garbage but the powernv code analyzes it nevertheless.
> 
> This initializes pcierr and fstate to zero in all call sites.
> 
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> Reviewed-by: Sam Bobroff <sbobroff@linux.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/c20577014f85f36d4e137d3d52a1f6

cheers

      parent reply	other threads:[~2018-12-23 14:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19  4:25 [PATCH kernel] powerpc/powernv/eeh/npu: Fix uninitialized variables in opal_pci_eeh_freeze_status Alexey Kardashevskiy
2018-11-19 23:28 ` Sam Bobroff
2018-11-20  2:51 ` Michael Ellerman
2018-11-20  3:51   ` Sam Bobroff
2018-11-20  6:55     ` Alexey Kardashevskiy
2018-11-20  6:59       ` Russell Currey
2018-11-20 10:58         ` Michael Ellerman
2018-12-23 13:28 ` Michael Ellerman [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=43N38m0TdCz9sNk@ozlabs.org \
    --to=patch-notifications@ellerman.id.au \
    --cc=aik@ozlabs.ru \
    --cc=alistair@popple.id.au \
    --cc=arbab@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oohall@gmail.com \
    --cc=pjaroszynski@nvidia.com \
    --cc=sbobroff@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).