From: hch@lst.de (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] drivers: dma-coherent: Introduce interface for default DMA pool
Date: Thu, 20 Jul 2017 16:11:09 +0200 [thread overview]
Message-ID: <20170720141109.GA14234@lst.de> (raw)
In-Reply-To: <d955cf45-1de4-91c5-6967-dcf46732abf6@arm.com>
On Thu, Jul 20, 2017 at 02:45:26PM +0100, Robin Murphy wrote:
> I'd have left the factored-out static helpers named __*_from_coherent(),
> as the _dev is not strictly true there, but it really doesn't matter as
> far as I'm concerned:
I've fixed that and a few other minor style bits up, and applied it
to the dma-mapping tree. If all goes right I'll send it to Linus
on Saturday.
next prev parent reply other threads:[~2017-07-20 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 10:19 [PATCH 0/2] Introduce interface for default DMA pool Vladimir Murzin
2017-07-20 10:19 ` [PATCH 1/2] drivers: dma-coherent: " Vladimir Murzin
2017-07-20 13:45 ` Robin Murphy
2017-07-20 14:11 ` Christoph Hellwig [this message]
2017-07-20 10:19 ` [PATCH 2/2] ARM: NOMMU: Wire-up default DMA interface Vladimir Murzin
2017-07-20 13:48 ` Robin Murphy
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=20170720141109.GA14234@lst.de \
--to=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.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).