linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Christophe Lombard <clombard@linux.vnet.ibm.com>,
	Vaibhav Jain <vaibhav@linux.vnet.ibm.com>,
	Frederic Barrat <fbarrat@linux.vnet.ibm.com>,
	stable@vger.kernel.org,
	Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] ocxl/afu_irq: Don't include <asm/pnv-ocxl.h>
Date: Thu, 20 Dec 2018 15:51:41 +0100	[thread overview]
Message-ID: <20181220155141.5fc73089@bahia.lan> (raw)
In-Reply-To: <59f00f99-0dcf-6da3-1672-b8614611db9b@au1.ibm.com>

On Tue, 11 Dec 2018 11:09:39 +1100
Andrew Donnellan <andrew.donnellan@au1.ibm.com> wrote:

> Acked-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
> 

Friendly ping before Xmas break :)

> On 11/12/18 2:13 am, Greg Kurz wrote:
> > The AFU irq code doesn't need to reach out to the platform.
> > 
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> >   drivers/misc/ocxl/afu_irq.c |    1 -
> >   1 file changed, 1 deletion(-)
> > 
> > diff --git a/drivers/misc/ocxl/afu_irq.c b/drivers/misc/ocxl/afu_irq.c
> > index e70cfa24577f..11ab996657a2 100644
> > --- a/drivers/misc/ocxl/afu_irq.c
> > +++ b/drivers/misc/ocxl/afu_irq.c
> > @@ -2,7 +2,6 @@
> >   // Copyright 2017 IBM Corp.
> >   #include <linux/interrupt.h>
> >   #include <linux/eventfd.h>
> > -#include <asm/pnv-ocxl.h>
> >   #include "ocxl_internal.h"
> >   #include "trace.h"
> >   
> >   
> 

  reply	other threads:[~2018-12-20 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 15:13 [PATCH] ocxl/afu_irq: Don't include <asm/pnv-ocxl.h> Greg Kurz
2018-12-10 15:56 ` Frederic Barrat
2018-12-11  0:09 ` Andrew Donnellan
2018-12-20 14:51   ` Greg Kurz [this message]
2018-12-22  9:54 ` 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=20181220155141.5fc73089@bahia.lan \
    --to=groug@kaod.org \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=clombard@linux.vnet.ibm.com \
    --cc=fbarrat@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=stable@vger.kernel.org \
    --cc=vaibhav@linux.vnet.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).