From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 3/3] powerpc/iommu: Support "hybrid" iommu/direct DMA ops for coherent_mask < dma_mask
Date: Sat, 25 Jul 2015 11:01:03 +1000 [thread overview]
Message-ID: <1437786063.7562.76.camel@kernel.crashing.org> (raw)
In-Reply-To: <55B2983E.5020300@linux.vnet.ibm.com>
On Fri, 2015-07-24 at 14:55 -0500, Brian King wrote:
> Ben,
>
> It looks like this patch has bit rot. I have a system now where I can test the
> latest version. Any chance you can rediff and resend and I can test?
Hrm, Michael didn't upstream it ? Ok, I'll have a look on monday.
(ping me if I don't).
Cheers,
Ben.
next prev parent reply other threads:[~2015-07-25 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 5:25 [PATCH 3/3] powerpc/iommu: Support "hybrid" iommu/direct DMA ops for coherent_mask < dma_mask Benjamin Herrenschmidt
2015-07-24 19:55 ` Brian King
2015-07-25 0:58 ` Michael Ellerman
2015-07-25 1:01 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-22 4:32 Benjamin Herrenschmidt
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=1437786063.7562.76.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=brking@linux.vnet.ibm.com \
--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).