From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: "BALATON Zoltan" <balaton@eik.bme.hu>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH 0/3] Misc sm501 clean ups
Date: Sun, 5 Feb 2023 06:40:00 -0300 [thread overview]
Message-ID: <498f0ba1-2f15-3b6e-cd6a-bb1ab86caad4@gmail.com> (raw)
In-Reply-To: <e4463a9e-f8de-aec1-f2ed-fae977049019@gmail.com>
On 1/30/23 06:43, Daniel Henrique Barboza wrote:
>
>
> On 1/28/23 23:43, BALATON Zoltan wrote:
>> On Mon, 23 Jan 2023, Philippe Mathieu-Daudé wrote:
>>> On 21/1/23 21:35, BALATON Zoltan wrote:
>>>> Some small trivial clean ups I've found while looking at this file.
>>>>
>>>> BALATON Zoltan (3):
>>>> hw/display/sm501: Remove parenthesis around consant macro definitions
>>>> hw/display/sm501: Remove unneeded casts from void pointer
>>>> hw/display/sm501: Code style fix
>>>>
>>>> hw/display/sm501.c | 419 +++++++++++++++++++++++----------------------
>>>> 1 file changed, 210 insertions(+), 209 deletions(-)
>>>
>>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>
>> Ping? Who will merge this series? Should Daniel take it via PPC or Gerd for display? I only care that it gets in one way or another and not lost between maintainers.
>
> I'm planning a PR at the end of this week. I can take these in.
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
>
> Thanks,
>
> Daniel
>
>>
>> Regards,
>> BALATON Zoltan
prev parent reply other threads:[~2023-02-05 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 20:35 [PATCH 0/3] Misc sm501 clean ups BALATON Zoltan
2023-01-21 20:35 ` [PATCH 1/3] hw/display/sm501: Remove parenthesis around consant macro definitions BALATON Zoltan
2023-01-21 20:35 ` [PATCH 2/3] hw/display/sm501: Remove unneeded casts from void pointer BALATON Zoltan
2023-01-21 20:35 ` [PATCH 3/3] hw/display/sm501: Code style fix BALATON Zoltan
2023-01-23 8:38 ` [PATCH 0/3] Misc sm501 clean ups Philippe Mathieu-Daudé
2023-01-29 2:43 ` BALATON Zoltan
2023-01-30 9:43 ` Daniel Henrique Barboza
2023-02-05 9:40 ` Daniel Henrique Barboza [this message]
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=498f0ba1-2f15-3b6e-cd6a-bb1ab86caad4@gmail.com \
--to=danielhb413@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).