From: "Alex Bennée" <alex.bennee@linaro.org>
To: Laurent Vivier <laurent@vivier.eu>
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2] linux-user/trace-events: fix minor typo in format string
Date: Thu, 17 Jun 2021 15:06:38 +0100 [thread overview]
Message-ID: <871r90fuu8.fsf@linaro.org> (raw)
In-Reply-To: <3005eb50-fa4b-4e10-2182-102e71f71f59@vivier.eu>
Laurent Vivier <laurent@vivier.eu> writes:
> Le 17/06/2021 à 14:20, Laurent Vivier a écrit :
>> Le 17/06/2021 à 13:47, Alex Bennée a écrit :
>>>
>>> Laurent Vivier <laurent@vivier.eu> writes:
>>>
>>>> Le 14/06/2021 à 16:42, Alex Bennée a écrit :
>>>>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>>>>>
>>>>> ---
>>>>> v2
>>>>> - fix typo in summary :-O
>>>>> ---
>>>>> linux-user/trace-events | 2 +-
>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/linux-user/trace-events b/linux-user/trace-events
>>>>> index 1ec0d11ee3..e7d2f54e94 100644
>>>>> --- a/linux-user/trace-events
>>>>> +++ b/linux-user/trace-events
>>>>> @@ -11,7 +11,7 @@ user_do_rt_sigreturn(void *env, uint64_t frame_addr) "env=%p frame_addr=0x%"PRIx
>>>>> user_do_sigreturn(void *env, uint64_t frame_addr) "env=%p frame_addr=0x%"PRIx64
>>>>> user_force_sig(void *env, int target_sig, int host_sig) "env=%p signal %d (host %d)"
>>>>> user_handle_signal(void *env, int target_sig) "env=%p signal %d"
>>>>> -user_host_signal(void *env, int host_sig, int target_sig) "env=%p signal %d (target %d("
>>>>> +user_host_signal(void *env, int host_sig, int target_sig) "env=%p signal %d (target %d)"
>>>>> user_queue_signal(void *env, int target_sig) "env=%p signal %d"
>>>>> user_s390x_restore_sigregs(void *env, uint64_t sc_psw_addr, uint64_t env_psw_addr) "env=%p frame psw.addr 0x%"PRIx64 " current psw.addr 0x%"PRIx64
>>>>>
>>>>>
>>>>
>>>> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
>>>
>>> Are you going to queue or shall I add it to my pile of "misc"?
>>>
>>>
>>
>> You can put it in your pile if you think you're going to do a pull request soon.
>>
>> I don't plan to do a trivial branch pull request before next week.
>
> But I'll try to do a linux-user one before...
Go for it, I have nothing cooking at the moment apart from a massive
re-base of the ARM refactor series :-/
--
Alex Bennée
next prev parent reply other threads:[~2021-06-17 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 14:42 [PATCH v2] linux-user/trace-events: fix minor typo in format string Alex Bennée
2021-06-14 15:03 ` Philippe Mathieu-Daudé
2021-06-16 13:21 ` Laurent Vivier
2021-06-17 11:47 ` Alex Bennée
2021-06-17 12:20 ` Laurent Vivier
2021-06-17 12:59 ` Laurent Vivier
2021-06-17 14:06 ` Alex Bennée [this message]
2021-06-17 14:09 ` 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=871r90fuu8.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=laurent@vivier.eu \
--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).