From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Stafford Horne <shorne-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jonas Bonn <jonas-A9uVI2HLR7kOP4wsBPIw7w@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stefan Kristiansson
<stefan.kristiansson-MbMCFXIvDHJFcC0YU169RA@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
openrisc-cunTk1MwBs9a3B2Vnqf2dGD2FQJk+8+b@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: use the generic dma-noncoherent code for openrisc
Date: Sat, 21 Jul 2018 14:37:08 +0200 [thread overview]
Message-ID: <20180721123708.GA635@lst.de> (raw)
In-Reply-To: <20180721053142.GC9742-Uk7Bhu+bUQgm0WYXfsLZQReHL2rgt/dS@public.gmane.org>
On Sat, Jul 21, 2018 at 02:31:42PM +0900, Stafford Horne wrote:
> For upstreaming, do you want me to send these through the openrisc tree, or do
> you want to send with the dma tree?
Feel free to merge them through the openrisc tree.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] use the generic dma-noncoherent code for openrisc
Date: Sat, 21 Jul 2018 14:37:08 +0200 [thread overview]
Message-ID: <20180721123708.GA635@lst.de> (raw)
In-Reply-To: <20180721053142.GC9742@lianli.shorne-pla.net>
On Sat, Jul 21, 2018 at 02:31:42PM +0900, Stafford Horne wrote:
> For upstreaming, do you want me to send these through the openrisc tree, or do
> you want to send with the dma tree?
Feel free to merge them through the openrisc tree.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Stafford Horne <shorne@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Jonas Bonn <jonas@southpole.se>,
Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
openrisc@lists.librecores.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: use the generic dma-noncoherent code for openrisc
Date: Sat, 21 Jul 2018 14:37:08 +0200 [thread overview]
Message-ID: <20180721123708.GA635@lst.de> (raw)
In-Reply-To: <20180721053142.GC9742@lianli.shorne-pla.net>
On Sat, Jul 21, 2018 at 02:31:42PM +0900, Stafford Horne wrote:
> For upstreaming, do you want me to send these through the openrisc tree, or do
> you want to send with the dma tree?
Feel free to merge them through the openrisc tree.
next prev parent reply other threads:[~2018-07-21 12:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 13:02 use the generic dma-noncoherent code for openrisc Christoph Hellwig
2018-07-19 13:02 ` [OpenRISC] " Christoph Hellwig
2018-07-19 13:02 ` [PATCH 1/4] openrisc: remove the sync_single_for_cpu DMA operation Christoph Hellwig
2018-07-19 13:02 ` [OpenRISC] " Christoph Hellwig
2018-07-19 13:02 ` [PATCH 2/4] openrisc: remove the no-op unmap_page and unmap_sg DMA operations Christoph Hellwig
2018-07-19 13:02 ` [OpenRISC] " Christoph Hellwig
2018-07-19 13:02 ` [PATCH 3/4] openrisc: fix cache maintainance the the sync_single_for_device DMA operation Christoph Hellwig
2018-07-19 13:02 ` [OpenRISC] " Christoph Hellwig
2018-07-19 13:02 ` [PATCH 4/4] openrisc: use generic dma_noncoherent_ops Christoph Hellwig
2018-07-19 13:02 ` [OpenRISC] " Christoph Hellwig
2018-07-21 5:31 ` use the generic dma-noncoherent code for openrisc Stafford Horne
2018-07-21 5:31 ` [OpenRISC] " Stafford Horne
[not found] ` <20180721053142.GC9742-Uk7Bhu+bUQgm0WYXfsLZQReHL2rgt/dS@public.gmane.org>
2018-07-21 12:37 ` Christoph Hellwig [this message]
2018-07-21 12:37 ` Christoph Hellwig
2018-07-21 12:37 ` [OpenRISC] " 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=20180721123708.GA635@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jonas-A9uVI2HLR7kOP4wsBPIw7w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=openrisc-cunTk1MwBs9a3B2Vnqf2dGD2FQJk+8+b@public.gmane.org \
--cc=shorne-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=stefan.kristiansson-MbMCFXIvDHJFcC0YU169RA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.