From: Christoph Hellwig <hch@lst.de>
To: Qian Cai <cai@lca.pw>
Cc: vladimir.murzin@arm.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, robin.murphy@arm.com,
hch@lst.de
Subject: Re: [PATCH] dma/coherent: remove unused dma_get_device_base()
Date: Tue, 1 Oct 2019 08:43:39 +0200 [thread overview]
Message-ID: <20191001064339.GA8582@lst.de> (raw)
In-Reply-To: <1569444877.5576.232.camel@lca.pw>
On Wed, Sep 25, 2019 at 04:54:37PM -0400, Qian Cai wrote:
> Ping. Please take a look at this trivial patch.
No need to rush. We just had the 5.4 merge window closing. I'll
queue this up in the dma-mapping for-next tree for 5.5 once I open it.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-10-01 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 13:00 [PATCH] dma/coherent: remove unused dma_get_device_base() Qian Cai
2019-09-25 20:54 ` Qian Cai
2019-10-01 6:43 ` Christoph Hellwig [this message]
2019-10-30 18:13 ` 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=20191001064339.GA8582@lst.de \
--to=hch@lst.de \
--cc=cai@lca.pw \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=vladimir.murzin@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).