From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Joe Perches <joe@perches.com>
Cc: linuxppc-dev@lists.ozlabs.org,
Gavin Shan <shangw@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eeh_pseries: Missing break?
Date: Sun, 9 Mar 2014 00:37:56 +0800 [thread overview]
Message-ID: <20140308163756.GA3766@shangw.(null)> (raw)
In-Reply-To: <1394296003.6972.26.camel@joe-AO722>
On Sat, Mar 08, 2014 at 08:26:43AM -0800, Joe Perches wrote:
>On Sun, 2014-03-09 at 00:16 +0800, Gavin Shan wrote:
>> On Fri, Mar 07, 2014 at 04:31:32PM -0800, Joe Perches wrote:
.../...
>English usages of "double negatives" are different
>than other languages. "it wasn't unintentional"
>means the same thing as "it was intentional".
>
Sorry, typo :)
>> Could you have better commit log
>> and subject, then repost it?
>>
.../...
>From my perspective, you should write up a commit
>message of your own choice (I wouldn't use "we",
>but the rest seems OK) and add a Reported-by:
>
>All I did was notice it and bring it to your
>attention.
>
Ok. I will post it. Thanks!
Thanks,
Gavin
>> >---
>> >diff --git a/arch/powerpc/platforms/pseries/eeh_pseries.c b/arch/powerpc/platforms/pseries/eeh_pseries.c
>> >index 8a8f047..83da53f 100644
>> >--- a/arch/powerpc/platforms/pseries/eeh_pseries.c
>> >+++ b/arch/powerpc/platforms/pseries/eeh_pseries.c
>> >@@ -460,14 +460,15 @@ static int pseries_eeh_get_state(struct eeh_pe *pe, int *state)
>> > case 5:
>> > if (rets[2]) {
>> > if (state) *state = rets[2];
>> > result = EEH_STATE_UNAVAILABLE;
>> > } else {
>> > result = EEH_STATE_NOT_SUPPORT;
>> > }
>> >+ break;
>> > default:
>> > result = EEH_STATE_NOT_SUPPORT;
>> > }
>> > } else {
>> > result = EEH_STATE_NOT_SUPPORT;
>> > }
>> >
>>
>> Thanks,
>> Gavin
>>
>
>
>
prev parent reply other threads:[~2014-03-08 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 0:31 [PATCH] eeh_pseries: Missing break? Joe Perches
2014-03-08 16:16 ` Gavin Shan
2014-03-08 16:26 ` Joe Perches
2014-03-08 16:37 ` Gavin Shan [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='20140308163756.GA3766@shangw.(null)' \
--to=shangw@linux.vnet.ibm.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).