From: Christoph Hellwig <hch@lst.de>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
alexander.h.duyck@linux.intel.com,
"open list:INTEL IOMMU (VT-d)" <iommu@lists.linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
Guenter Roeck <linux@roeck-us.net>,
Greg KH <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] dma-direct: Fix return value of dma_direct_supported
Date: Fri, 5 Oct 2018 09:17:36 +0200 [thread overview]
Message-ID: <20181005071736.GA24011@lst.de> (raw)
In-Reply-To: <CAKgT0UfbAokpR=-xrfNjeYMroEDH4HtPgM6qK_nWmBqK3QOf6A@mail.gmail.com>
On Thu, Oct 04, 2018 at 08:13:26AM -0700, Alexander Duyck wrote:
> Thanks for the review.
>
> - Alex
>
> P.S. It looks like I forgot to add Christoph to the original mail
> since I had just copied the To and Cc from the original submission, so
> I added him to the Cc for this.
Yes, there was some oddness with replies appearing out of nowhere that
I couldn't understand in my jetlagged state yesterday. Now thay I've
caught up on iommu list traffic it all makes sense now. I've applied
this with an Acked-by for Robin added based on his reply.
next prev parent reply other threads:[~2018-10-05 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 23:48 [PATCH] dma-direct: Fix return value of dma_direct_supported Alexander Duyck
2018-10-04 11:25 ` Robin Murphy
2018-10-04 15:13 ` Alexander Duyck
2018-10-05 7:17 ` Christoph Hellwig [this message]
2018-12-13 19:45 ` Lendacky, Thomas
2018-12-13 19:58 ` Christoph Hellwig
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=20181005071736.GA24011@lst.de \
--to=hch@lst.de \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robin.murphy@arm.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).