From: "Eugenio Pérez" <eperezma@redhat.com>
To: qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-trivial@nongnu.org, Jason Wang <jasowang@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Peter Xu <peterx@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH v2 0/1] util: Make some iova_tree functions parameters const
Date: Wed, 13 Oct 2021 20:27:12 +0200 [thread overview]
Message-ID: <20211013182713.888753-1-eperezma@redhat.com> (raw)
Some guidelines misses I found while working on Shadow Virtqueue, that
uses these functions at this moment.
v2:
* Add a missed const in iova_tree_find_address.
Eugenio Pérez (1):
util: Make some iova_tree parameters const
include/qemu/iova-tree.h | 8 ++++----
hw/i386/intel_iommu.c | 2 +-
util/iova-tree.c | 12 ++++++------
3 files changed, 11 insertions(+), 11 deletions(-)
--
2.27.0
next reply other threads:[~2021-10-13 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 18:27 Eugenio Pérez [this message]
2021-10-13 18:27 ` [PATCH v2 1/1] util: Make some iova_tree parameters const Eugenio Pérez
2021-10-15 10:41 ` Paolo Bonzini
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=20211013182713.888753-1-eperezma@redhat.com \
--to=eperezma@redhat.com \
--cc=ehabkost@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.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).