From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] memory: Display MemoryRegion name in read/write ops trace events
Date: Mon, 21 Jun 2021 14:17:53 +0200 [thread overview]
Message-ID: <89e922a4-a22d-89ea-f6db-3181e7c2e7ca@amsat.org> (raw)
In-Reply-To: <c1f1313c-6d32-c560-30e6-0acd8a6f2090@vivier.eu>
On 6/21/21 12:13 PM, Laurent Vivier wrote:
> Le 21/06/2021 à 12:08, Philippe Mathieu-Daudé a écrit :
>> Hi Laurent,
>>
>> On 6/7/21 1:29 PM, Laurent Vivier wrote:
>>> Le 07/06/2021 à 10:28, Philippe Mathieu-Daudé a écrit :
>>>> On 6/7/21 9:33 AM, Laurent Vivier wrote:
>>>>> Le 02/06/2021 à 12:49, Philippe Mathieu-Daudé a écrit :
>>>>>> Cc'ing qemu-trivial@
>>>
>>> So it looks good.
>>
>> Is there something else you expect me to do with this patch?
>> Maybe you expect another R-b to take it, so I should keep
>> pinging for review?
>>
>
> No, I'm working on a linux-user pull request, once done I'll do a new trivial branch pull request.
No hurry, I just wanted to know if there was something missing on my side :)
>
> Thanks,
> Laurent
>
next prev parent reply other threads:[~2021-06-21 12:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 7:48 [PATCH] memory: Display MemoryRegion name in read/write ops trace events Philippe Mathieu-Daudé
2021-03-18 15:39 ` Philippe Mathieu-Daudé
2021-06-02 10:49 ` Philippe Mathieu-Daudé
2021-06-07 7:33 ` Laurent Vivier
2021-06-07 8:28 ` Philippe Mathieu-Daudé
2021-06-07 11:29 ` Laurent Vivier
2021-06-21 10:08 ` Philippe Mathieu-Daudé
2021-06-21 10:13 ` Laurent Vivier
2021-06-21 12:17 ` Philippe Mathieu-Daudé [this message]
2021-07-09 9:03 ` Laurent Vivier
2021-06-05 19:26 ` Laurent Vivier
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=89e922a4-a22d-89ea-f6db-3181e7c2e7ca@amsat.org \
--to=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=pbonzini@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 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).