qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: "Eugenio Pérez" <eperezma@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Yan Zhao <yan.y.zhao@intel.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	qemu-devel@nongnu.org, Eric Auger <eric.auger@redhat.com>,
	qemu-arm@nongnu.org, Avi Kivity <avi@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [RFC v4 1/2] memory: Rename memory_region_notify_one to memory_region_notify_one_iommu
Date: Wed, 19 Aug 2020 12:38:46 -0400	[thread overview]
Message-ID: <20200819163846.GA305409@xz-x1> (raw)
In-Reply-To: <20200818130151.31678-2-eperezma@redhat.com>

On Tue, Aug 18, 2020 at 03:01:50PM +0200, Eugenio Pérez wrote:
> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>

Reviewed-by: Peter Xu <peterx@redhat.com>

It would be good if there's some commit message, though..

Also, I'd slightly prefer memory_region_notify_iommu_one rather than one_iommu,
but I'm fine with either.

-- 
Peter Xu



  reply	other threads:[~2020-08-19 16:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 13:01 [RFC v4 0/2] memory: Delete assertion in memory_region_unregister_iommu_notifier Eugenio Pérez
2020-08-18 13:01 ` [RFC v4 1/2] memory: Rename memory_region_notify_one to memory_region_notify_one_iommu Eugenio Pérez
2020-08-19 16:38   ` Peter Xu [this message]
2020-08-18 13:01 ` [RFC v4 2/2] memory: Skip bad range assertion if notifier is DEVIOTLB type Eugenio Pérez
2020-08-19 16:40   ` Peter Xu
2020-08-19 17:47     ` Eugenio Perez Martin
2020-08-19 17:53       ` Eugenio Perez Martin
2020-08-19 18:25       ` Peter Xu

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=20200819163846.GA305409@xz-x1 \
    --to=peterx@redhat.com \
    --cc=avi@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=eric.auger@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=rth@twiddle.net \
    --cc=yan.y.zhao@intel.com \
    /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).