From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Alastair D'Silva" <alastair@au1.ibm.com>, alastair@d-silva.org
Cc: Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
Frederic Barrat <fbarrat@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v4 1/7] ocxl: Split pci.c
Date: Fri, 3 May 2019 16:59:10 +1000 (AEST) [thread overview]
Message-ID: <44wNKC2Pt1z9sP8@ozlabs.org> (raw)
In-Reply-To: <20190327053137.15173-2-alastair@au1.ibm.com>
On Wed, 2019-03-27 at 05:31:30 UTC, "Alastair D'Silva" wrote:
> From: Alastair D'Silva <alastair@d-silva.org>
>
> In preparation for making core code available for external drivers,
> move the core code out of pci.c and into core.c
>
> Signed-off-by: Alastair D'Silva <alastair@d-silva.org>
> Acked-by: Frederic Barrat <fbarrat@linux.ibm.com>
> Acked-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/1ba2143606a10f1c2e7308bc7abd940a
cheers
next prev parent reply other threads:[~2019-05-03 6:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 5:31 [PATCH v4 0/7] Refactor OCXL driver to allow external drivers to use it Alastair D'Silva
2019-03-27 5:31 ` [PATCH v4 1/7] ocxl: Split pci.c Alastair D'Silva
2019-04-17 13:22 ` Frederic Barrat
2019-04-30 4:20 ` Andrew Donnellan
2019-05-03 6:59 ` Michael Ellerman [this message]
2019-03-27 5:31 ` [PATCH v4 2/7] ocxl: Don't pass pci_dev around Alastair D'Silva
2019-04-17 13:29 ` Frederic Barrat
2019-04-30 4:25 ` Andrew Donnellan
2019-03-27 5:31 ` [PATCH v4 3/7] ocxl: Create a clear delineation between ocxl backend & frontend Alastair D'Silva
2019-04-17 15:29 ` Frederic Barrat
2019-03-27 5:31 ` [PATCH v4 4/7] ocxl: Allow external drivers to use OpenCAPI contexts Alastair D'Silva
2019-04-17 15:33 ` Frederic Barrat
2019-03-27 5:31 ` [PATCH v4 5/7] ocxl: afu_irq only deals with IRQ IDs, not offsets Alastair D'Silva
2019-04-17 15:33 ` Frederic Barrat
2019-03-27 5:31 ` [PATCH v4 6/7] ocxl: move event_fd handling to frontend Alastair D'Silva
2019-04-17 15:33 ` Frederic Barrat
2019-03-27 5:31 ` [PATCH v4 7/7] ocxl: Provide global MMIO accessors for external drivers Alastair D'Silva
2019-04-17 15:35 ` Frederic Barrat
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=44wNKC2Pt1z9sP8@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=alastair@au1.ibm.com \
--cc=alastair@d-silva.org \
--cc=andrew.donnellan@au1.ibm.com \
--cc=arnd@arndb.de \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--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