From: Joerg Roedel <jroedel@suse.de>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Christoph Hellwig <hch@lst.de>,
benh@kernel.crashing.org, KVM <kvm@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
dwmw2@infradead.org, Sebastian Ott <sebott@linux.vnet.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
Michael Tsirkin <mst@redhat.com>
Subject: Re: [PATCH 1/3] dma: Provide simple noop dma ops
Date: Thu, 5 Nov 2015 14:31:30 +0100 [thread overview]
Message-ID: <20151105133130.GB2255@suse.de> (raw)
In-Reply-To: <1446551679-33492-2-git-send-email-borntraeger@de.ibm.com>
On Tue, Nov 03, 2015 at 12:54:37PM +0100, Christian Borntraeger wrote:
> We are going to require dma_ops for several common drivers, even for
> systems that do have an identity mapping. Lets provide some minimal
> no-op dma_ops that can be used for that purpose.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> include/linux/dma-mapping.h | 2 ++
> lib/Makefile | 1 +
> lib/dma-noop.c | 75 +++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 78 insertions(+)
> create mode 100644 lib/dma-noop.c
Reviewed-by: Joerg Roedel <jroedel@suse.de>
next prev parent reply other threads:[~2015-11-05 13:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 11:54 [PATCHv3 0/3] dma ops and virtio Christian Borntraeger
2015-11-03 11:54 ` [PATCH 1/3] dma: Provide simple noop dma ops Christian Borntraeger
2015-11-05 13:31 ` Joerg Roedel [this message]
2015-11-05 13:31 ` Joerg Roedel
2015-11-03 11:54 ` [PATCH 2/3] alpha/dma: use common " Christian Borntraeger
2015-11-03 11:54 ` Christian Borntraeger
2015-11-03 11:54 ` [PATCH 3/3] s390/dma: Allow per device " Christian Borntraeger
2015-11-03 11:54 ` Christian Borntraeger
2015-11-03 12:26 ` Cornelia Huck
2015-11-05 9:33 ` Christian Borntraeger
2015-11-05 19:22 ` Andy Lutomirski
2015-11-05 19:22 ` Andy Lutomirski
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=20151105133130.GB2255@suse.de \
--to=jroedel@suse.de \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.ibm.com \
--cc=virtualization@lists.linux-foundation.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.