From: Robin Murphy <robin.murphy@arm.com>
To: Christoph Hellwig <hch@lst.de>, iommu@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: fix up nowarn confusion in the dma mapping layer
Date: Tue, 9 Oct 2018 13:55:03 +0100 [thread overview]
Message-ID: <8da56b4f-0625-cb44-fa21-d7c1c04a56b0@arm.com> (raw)
In-Reply-To: <20181008070358.GA3182@lst.de>
On 08/10/18 08:03, Christoph Hellwig wrote:
> Any comments on these rather trivial patches?
Nope ;)
For both,
Acked-by: Robin Murphy <robin.murphy@arm.com>
> On Mon, Oct 01, 2018 at 01:12:55PM -0700, Christoph Hellwig wrote:
>> Hi all,
>>
>> this series sorts out how we deal with the nowarn flags in the dma
>> mapping code. We still support __GFP_NOWARN for the legacy APIs that
>> don't support passing the dma specific flags, but we generally want
>> every implementation to actually check DMA_ATTR_NO_WARN instead.
>> _______________________________________________
>> iommu mailing list
>> iommu@lists.linux-foundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/iommu
> ---end quoted text---
>
prev parent reply other threads:[~2018-10-09 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 20:12 fix up nowarn confusion in the dma mapping layer Christoph Hellwig
2018-10-01 20:12 ` [PATCH 1/2] dma-mapping: translate __GFP_NOFAIL to DMA_ATTR_NO_WARN Christoph Hellwig
2018-10-01 20:12 ` [PATCH 2/2] dma-direct: respect DMA_ATTR_NO_WARN Christoph Hellwig
2018-10-08 7:03 ` fix up nowarn confusion in the dma mapping layer Christoph Hellwig
2018-10-09 12:55 ` Robin Murphy [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=8da56b4f-0625-cb44-fa21-d7c1c04a56b0@arm.com \
--to=robin.murphy@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.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).