qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 0/3] pci: Let PCI DMA API functions propagate a MemTxResult
Date: Tue, 15 Sep 2020 19:30:01 +0200	[thread overview]
Message-ID: <00303be5-8ddb-be84-0d15-3ea537f275e2@redhat.com> (raw)
In-Reply-To: <20200904162620.657726-1-philmd@redhat.com>

On 9/4/20 6:26 PM, Philippe Mathieu-Daudé wrote:
> The DMA API propagates MemTxResult:
> - MEMTX_OK,
> - MEMTX_device_ERROR,
> - MEMTX_DECODE_ERROR.
> 
> Let the PCI DMA API propagate them, as they are
> clearer than an undocumented 'int'.
> 
> Based-on: <20200904154439.643272-1-philmd@redhat.com>
> https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg02048.html
> 
> Philippe Mathieu-Daudé (3):
>   pci: Let pci_dma_rw() propagate MemTxResult
>   pci: Let pci_dma_read() propagate MemTxResult
>   pci: Let pci_dma_write() propagate MemTxResult
> 
>  include/hw/pci/pci.h | 50 ++++++++++++++++++++++++++++++++++++++------
>  1 file changed, 44 insertions(+), 6 deletions(-)
> 

This series is fully review.

Paolo, if you take the DMA series on which this one
is based, could you take this too?

Thanks :)



      parent reply	other threads:[~2020-09-15 17:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 16:26 [PATCH 0/3] pci: Let PCI DMA API functions propagate a MemTxResult Philippe Mathieu-Daudé
2020-09-04 16:26 ` [PATCH 1/3] pci: Let pci_dma_rw() propagate MemTxResult Philippe Mathieu-Daudé
2020-09-05  2:41   ` Li Qiang
2020-09-06  4:06   ` Richard Henderson
2020-09-04 16:26 ` [PATCH 2/3] pci: Let pci_dma_read() " Philippe Mathieu-Daudé
2020-09-05  2:42   ` Li Qiang
2020-09-06  4:07   ` Richard Henderson
2020-09-04 16:26 ` [PATCH 3/3] pci: Let pci_dma_write() " Philippe Mathieu-Daudé
2020-09-05  2:42   ` Li Qiang
2020-09-06  4:08   ` Richard Henderson
2020-09-15 17:30 ` Philippe Mathieu-Daudé [this message]

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=00303be5-8ddb-be84-0d15-3ea537f275e2@redhat.com \
    --to=philmd@redhat.com \
    --cc=mst@redhat.com \
    --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).