linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: cbe-oss-dev@lists.ozlabs.org, arnd@arndb.de, greg@kroah.com,
	imunsie@au.ibm.com, linux-kernel@vger.kernel.org,
	linuxppc-dev@ozlabs.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	anton@samba.org, jk@ozlabs.org
Subject: Re: [PATCH v3 01/16] powerpc/cell: Move spu_handle_mm_fault() out of cell platform
Date: Tue, 07 Oct 2014 22:34:00 +1100	[thread overview]
Message-ID: <1412681640.4133.0.camel@ale.ozlabs.ibm.com> (raw)
In-Reply-To: <20141007220855.75b64a57@canb.auug.org.au>


> > +int copro_data_segment(struct mm_struct *mm, u64 ea, u64 *esid, u64 *v=
sid);
>=20
> This function is otherwise not included in this patch, so it should
> probably be removed (as the next patch removes it anyway).

Yeah, looks like I screwed it up slightly in the packing of these
patches.

Thanks.
Mikey

  reply	other threads:[~2014-10-07 11:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 10:48 [PATCH v3 0/16] POWER8 Coherent Accelerator device driver Michael Neuling
2014-10-07 10:48 ` [PATCH v3 01/16] powerpc/cell: Move spu_handle_mm_fault() out of cell platform Michael Neuling
2014-10-07 11:08   ` Stephen Rothwell
2014-10-07 11:34     ` Michael Neuling [this message]
2014-10-07 10:48 ` [PATCH v3 02/16] powerpc/cell: Move data segment faulting code " Michael Neuling
2014-10-07 10:48 ` [PATCH v3 03/16] powerpc/cell: Make spu_flush_all_slbs() generic Michael Neuling
2014-10-07 10:48 ` [PATCH v3 04/16] powerpc/msi: Improve IRQ bitmap allocator Michael Neuling
2014-10-07 10:48 ` [PATCH v3 05/16] powerpc/mm: Export mmu_kernel_ssize and mmu_linear_psize Michael Neuling
2014-10-07 10:48 ` [PATCH v3 06/16] powerpc/powernv: Split out set MSI IRQ chip code Michael Neuling
2014-10-07 10:48 ` [PATCH v3 07/16] cxl: Add new header for call backs and structs Michael Neuling
2014-10-07 10:48 ` [PATCH v3 08/16] powerpc/powerpc: Add new PCIe functions for allocating cxl interrupts Michael Neuling
2014-10-07 22:59   ` [v3, " Michael Ellerman
2014-10-08  0:46     ` Michael Neuling
2014-10-07 10:48 ` [PATCH v3 09/16] powerpc/mm: Add new hash_page_mm() Michael Neuling
2014-10-07 10:48 ` [PATCH v3 10/16] powerpc/opal: Add PHB to cxl mode call Michael Neuling
2014-10-07 10:48 ` [PATCH v3 11/16] powerpc/mm: Add hooks for cxl Michael Neuling
2014-10-07 10:48 ` [PATCH v3 12/16] cxl: Add base builtin support Michael Neuling
2014-10-07 23:04   ` [v3,12/16] " Michael Ellerman
2014-10-08  0:45     ` Michael Neuling
2014-10-07 10:48 ` [PATCH v3 13/16] cxl: Driver code for powernv PCIe based cards for userspace access Michael Neuling
2014-10-07 10:48 ` [PATCH v3 14/16] cxl: Userspace header file Michael Neuling
2014-10-07 10:48 ` [PATCH v3 15/16] cxl: Add driver to Kbuild and Makefiles Michael Neuling
2014-10-07 10:48 ` [PATCH v3 16/16] cxl: Add documentation for userspace APIs Michael Neuling
2014-10-08  5:36   ` [v3,16/16] " 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=1412681640.4133.0.camel@ale.ozlabs.ibm.com \
    --to=mikey@neuling.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=anton@samba.org \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@lists.ozlabs.org \
    --cc=greg@kroah.com \
    --cc=imunsie@au.ibm.com \
    --cc=jk@ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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).