From: Kevin Wolf <kwolf@redhat.com>
To: Klaus Birkelund Jensen <klaus@birkelund.eu>
Cc: Keith Busch <keith.busch@intel.com>,
"Heitke, Kenneth" <kenneth.heitke@intel.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] nvme: fix copy direction in DMA reads going to CMB
Date: Mon, 20 May 2019 12:11:04 +0200 [thread overview]
Message-ID: <20190520101104.GC5699@localhost.localdomain> (raw)
In-Reply-To: <20190518073905.17178-1-klaus@birkelund.eu>
Am 18.05.2019 um 09:39 hat Klaus Birkelund Jensen geschrieben:
> `nvme_dma_read_prp` erronously used `qemu_iovec_*to*_buf` instead of
> `qemu_iovec_*from*_buf` when the request involved the controller memory
> buffer.
>
> Signed-off-by: Klaus Birkelund Jensen <klaus.jensen@cnexlabs.com>
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2019-05-20 10:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 7:39 [Qemu-devel] [PATCH] nvme: fix copy direction in DMA reads going to CMB Klaus Birkelund Jensen
2019-05-18 17:56 ` Heitke, Kenneth
2019-05-20 10:11 ` Kevin Wolf [this message]
2019-05-20 15:05 ` Keith Busch
2019-05-20 17:56 ` Klaus Birkelund
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=20190520101104.GC5699@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=keith.busch@intel.com \
--cc=kenneth.heitke@intel.com \
--cc=klaus@birkelund.eu \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).