From: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
To: Russell Currey <ruscur@russell.cc>, linuxppc-dev@lists.ozlabs.org
Cc: aik@ozlabs.ru
Subject: Re: [PATCH v3 2/2] powerpc/eeh: Clean up and document event handling functions
Date: Thu, 20 Apr 2017 10:36:41 +1000 [thread overview]
Message-ID: <aa65f593-2c0d-47ef-df9a-bc99a6460f78@au1.ibm.com> (raw)
In-Reply-To: <20170419073927.29224-2-ruscur@russell.cc>
On 19/04/17 17:39, Russell Currey wrote:
> Remove unnecessary tags in eeh_handle_normal_event(), and add function
> comments for eeh_handle_normal_event() and eeh_handle_special_event().
>
> The only functional difference is that in the case of a PE reaching the
> maximum number of failures, rather than one message telling you of this
> and suggesting you reseat the device, there are two separate messages.
>
> Suggested-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> Signed-off-by: Russell Currey <ruscur@russell.cc>
Reviewed-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
--
Andrew Donnellan OzLabs, ADL Canberra
andrew.donnellan@au1.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2017-04-20 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 7:39 [PATCH v3 1/2] powerpc/eeh: Avoid use after free in eeh_handle_special_event() Russell Currey
2017-04-19 7:39 ` [PATCH v3 2/2] powerpc/eeh: Clean up and document event handling functions Russell Currey
2017-04-19 23:48 ` Gavin Shan
2017-04-20 1:03 ` Russell Currey
2017-04-20 1:26 ` Gavin Shan
2017-04-20 0:36 ` Andrew Donnellan [this message]
2017-04-20 1:24 ` Gavin Shan
2017-05-03 22:18 ` [v3, " Michael Ellerman
2017-04-19 23:49 ` [PATCH v3 1/2] powerpc/eeh: Avoid use after free in eeh_handle_special_event() Gavin Shan
2017-05-03 22:18 ` [v3, " Michael Ellerman
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=aa65f593-2c0d-47ef-df9a-bc99a6460f78@au1.ibm.com \
--to=andrew.donnellan@au1.ibm.com \
--cc=aik@ozlabs.ru \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ruscur@russell.cc \
/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).