From: Michael Ellerman <mpe@ellerman.id.au>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [1/3] powerpc/iommu: Remove dma_data union
Date: Thu, 16 Jul 2015 20:01:00 +1000 (AEST) [thread overview]
Message-ID: <20150716100100.EB1FA1402C2@ozlabs.org> (raw)
In-Reply-To: <1435123522.3996.29.camel@kernel.crashing.org>
On Wed, 2015-24-06 at 05:25:22 UTC, Benjamin Herrenschmidt wrote:
> To support "hybrid" DMA ops in a subsequent patch, we will need both
> a direct DMA offset and an iommu pointer. Those are currently exclusive
> (a union), so change them to be separate fields.
>
> While there, also type iommu_table_base properly and make exist only
> on CONFIG_PPC64 since it's not referenced on 32-bit at all.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/2db4928bb559f8b43ca7
cheers
prev parent reply other threads:[~2015-07-16 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 5:25 [PATCH 1/3] powerpc/iommu: Remove dma_data union Benjamin Herrenschmidt
2015-07-16 10:01 ` Michael Ellerman [this message]
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=20150716100100.EB1FA1402C2@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).