From: Christoph Hellwig <hch@lst.de>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] use the generic dma-noncoherent code for openrisc
Date: Thu, 19 Jul 2018 06:02:28 -0700 [thread overview]
Message-ID: <20180719130232.1819-1-hch@lst.de> (raw)
Hi Openrisc maintainers,
can you review these patches to switch openrisc to use the generic
dma-noncoherent code? All the requirements are in mainline already
and we've switched various architectures over to it already.
next reply other threads:[~2018-07-19 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 13:02 Christoph Hellwig [this message]
2018-07-19 13:02 ` [OpenRISC] [PATCH 1/4] openrisc: remove the sync_single_for_cpu DMA operation Christoph Hellwig
2018-07-19 13:02 ` [OpenRISC] [PATCH 2/4] openrisc: remove the no-op unmap_page and unmap_sg DMA operations Christoph Hellwig
2018-07-19 13:02 ` [OpenRISC] [PATCH 3/4] openrisc: fix cache maintainance the the sync_single_for_device DMA operation Christoph Hellwig
2018-07-19 13:02 ` [OpenRISC] [PATCH 4/4] openrisc: use generic dma_noncoherent_ops Christoph Hellwig
2018-07-21 5:31 ` [OpenRISC] use the generic dma-noncoherent code for openrisc Stafford Horne
2018-07-21 12:37 ` 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=20180719130232.1819-1-hch@lst.de \
--to=hch@lst.de \
--cc=openrisc@lists.librecores.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).