public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah•com>
To: Andrew Donnellan <andrew.donnellan@au1•ibm.com>
Cc: Michael Ellerman <patch-notifications@ellerman•id.au>,
	linuxppc-dev@lists•ozlabs.org, stable@vger•kernel.org,
	ukrishn@linux•vnet.ibm.com, vaibhav@linux•vnet.ibm.com,
	fbarrat@linux•vnet.ibm.com, imunsie@au1•ibm.com
Subject: Re: [v2] cxl: prevent read/write to AFU config space while AFU not configured
Date: Mon, 6 Feb 2017 10:43:56 +0100	[thread overview]
Message-ID: <20170206094356.GA8583@kroah.com> (raw)
In-Reply-To: <f3a508e9-3c23-f929-7b81-fd803c920095@au1.ibm.com>

On Mon, Feb 06, 2017 at 12:15:59PM +1100, Andrew Donnellan wrote:
> On 27/01/17 11:57, Andrew Donnellan wrote:
> > On 27/01/17 11:40, Michael Ellerman wrote:
> > > Applied to powerpc next, thanks.
> > > 
> > > https://git.kernel.org/powerpc/c/14a3ae34bfd0bcb1cc12d55b06a858
> > 
> > Will fix the remaining locking issue in a follow up patch...
> 
> Stable team - please make sure this doesn't go in without
> http://patchwork.ozlabs.org/patch/724315/ once that's merged.

Ok, hopefully they show up in Linus's tree at the same time :)

thanks,

greg k-h

  reply	other threads:[~2017-02-06  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09  6:18 [PATCH v2] cxl: prevent read/write to AFU config space while AFU not configured Andrew Donnellan
2016-12-09 16:30 ` Frederic Barrat
2016-12-13  6:11   ` Andrew Donnellan
2017-01-27  0:40 ` [v2] " Michael Ellerman
2017-01-27  0:57   ` Andrew Donnellan
2017-02-06  1:15     ` Andrew Donnellan
2017-02-06  9:43       ` Greg KH [this message]
2017-02-07  2:15         ` 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=20170206094356.GA8583@kroah.com \
    --to=greg@kroah$(echo .)com \
    --cc=andrew.donnellan@au1$(echo .)ibm.com \
    --cc=fbarrat@linux$(echo .)vnet.ibm.com \
    --cc=imunsie@au1$(echo .)ibm.com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=patch-notifications@ellerman$(echo .)id.au \
    --cc=stable@vger$(echo .)kernel.org \
    --cc=ukrishn@linux$(echo .)vnet.ibm.com \
    --cc=vaibhav@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