public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Andrew Donnellan <andrew.donnellan@au1•ibm.com>
To: Michael Ellerman <mpe@ellerman•id.au>, linuxppc-dev@ozlabs•org
Cc: Gavin Shan <gwshan@linux•vnet.ibm.com>, Daniel Axtens <dja@axtens•net>
Subject: Re: powerpc/eeh: eeh_pci_enable(): fix checking of post-request state
Date: Tue, 8 Mar 2016 18:42:56 +1100	[thread overview]
Message-ID: <56DE8280.6020302@au1.ibm.com> (raw)
In-Reply-To: <56B92B74.8040108@au1.ibm.com>

On 09/02/16 10:57, Andrew Donnellan wrote:
> It is a fix - I'm a bit hazy on the details now but IIRC, Daniel Axtens
> and I encountered this when doing some cxl debugging, though I think we
> decided not to tag this for stable since it was a secondary issue to the
> primary bug we were looking for. It probably could go to stable though?
> (Daniel - thoughts?)
>
> The line in question was last touched in 4d4f577e4b5e, but it looks like
> the behaviour wasn't right even before that.

Ping :)

I think this patch should still go in, I don't really care whether it 
goes to stable or not.

-- 
Andrew Donnellan              Software Engineer, OzLabs
andrew.donnellan@au1•ibm.com  Australia Development Lab, Canberra
+61 2 6201 8874 (work)        IBM Australia Limited

  reply	other threads:[~2016-03-08  7:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23  6:19 [PATCH] powerpc/eeh: eeh_pci_enable(): fix checking of post-request state Andrew Donnellan
2015-10-24  1:23 ` Gavin Shan
2015-10-26 23:05 ` Daniel Axtens
2015-10-26 23:09 ` Daniel Axtens
2016-02-08 11:37 ` Michael Ellerman
2016-02-08 23:57   ` Andrew Donnellan
2016-03-08  7:42     ` Andrew Donnellan [this message]
2016-03-08 22:14       ` Gavin Shan
2016-03-09 12:51 ` 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=56DE8280.6020302@au1.ibm.com \
    --to=andrew.donnellan@au1$(echo .)ibm.com \
    --cc=dja@axtens$(echo .)net \
    --cc=gwshan@linux$(echo .)vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs$(echo .)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