From: Laurent Vivier <lvivier@redhat.com>
To: Peter Xu <peterx@redhat.com>, Eugenio Perez Martin <eperezma@redhat.com>
Cc: qemu-level <qemu-devel@nongnu.org>,
qemu-trivial@nongnu.org, Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] util: Return void on iova_tree_remove
Date: Thu, 12 May 2022 18:53:09 +0200 [thread overview]
Message-ID: <8310cc7f-8c9c-9411-3c6a-ab416f79d8b9@redhat.com> (raw)
In-Reply-To: <Yn0vz+6nYs0d/Hvj@xz-m1.local>
On 12/05/2022 18:03, Peter Xu wrote:
> On Thu, May 12, 2022 at 05:48:47PM +0200, Eugenio Perez Martin wrote:
>> On Wed, Apr 27, 2022 at 5:50 PM Eugenio Pérez <eperezma@redhat.com> wrote:
>>>
>>> It always returns IOVA_OK so nobody uses it.
>>>
>>> Acked-by: Jason Wang <jasowang@redhat.com>
>>> Reviewed-by: Peter Xu <peterx@redhat.com>
>>> Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
>>
>> Hi! Friendly ping about this, is it something pending from my side?
>
> Don't think so. :)
>
> This patch does look fine to go via trivial branch, Laurent?
>
> Also copying Michael since for other iova-tree change it always go via
> Michael before.
>
I can take it via qemu-trivial.
Thanks,
Laurent
next prev parent reply other threads:[~2022-05-12 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 15:49 [PATCH] util: Return void on iova_tree_remove Eugenio Pérez
2022-05-12 15:48 ` Eugenio Perez Martin
2022-05-12 16:03 ` Peter Xu
2022-05-12 16:53 ` Laurent Vivier [this message]
2022-06-28 8:57 ` Laurent Vivier
-- strict thread matches above, loose matches on Subject: below --
2022-03-31 18:17 Eugenio Pérez
2022-03-31 18:30 ` Peter Xu
2022-04-01 2:30 ` Jason Wang
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=8310cc7f-8c9c-9411-3c6a-ab416f79d8b9@redhat.com \
--to=lvivier@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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 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.