From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] hw/display/cirrus_vga: Fix code mis-indentation
Date: Sat, 30 May 2020 19:41:23 +0200 [thread overview]
Message-ID: <17c858f1-dbd0-42b9-f2fa-22954133891a@redhat.com> (raw)
In-Reply-To: <20200529165436.23573-1-f4bug@amsat.org>
On 29/05/2020 18.54, Philippe Mathieu-Daudé wrote:
> While replacing fprintf() by qemu_log_mask() in commit
> 2b55f4d3504, we incorrectly used a 'tab = 4 spaces'
> alignment, leading to misindented new code. Fix now.
>
> Reported-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> hw/display/cirrus_vga.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
> index 92c197cdde..212d6f5e61 100644
> --- a/hw/display/cirrus_vga.c
> +++ b/hw/display/cirrus_vga.c
> @@ -1032,9 +1032,9 @@ static void cirrus_bitblt_start(CirrusVGAState * s)
> } else {
> if (s->cirrus_blt_mode & CIRRUS_BLTMODE_TRANSPARENTCOMP) {
> if (s->cirrus_blt_pixelwidth > 2) {
> - qemu_log_mask(LOG_GUEST_ERROR,
> - "cirrus: src transparent without colorexpand "
> - "must be 8bpp or 16bpp\n");
> + qemu_log_mask(LOG_GUEST_ERROR,
> + "cirrus: src transparent without colorexpand "
> + "must be 8bpp or 16bpp\n");
> goto bitblt_ignore;
> }
> if (s->cirrus_blt_mode & CIRRUS_BLTMODE_BACKWARDS) {
>
I think it would be better to fix the TABs in the whole surounding area,
too. Or maybe even in the whole file. Otherwise this problem will happen
soon again...
Thomas
next prev parent reply other threads:[~2020-05-30 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 16:54 [PATCH] hw/display/cirrus_vga: Fix code mis-indentation Philippe Mathieu-Daudé
2020-05-30 17:41 ` Thomas Huth [this message]
2020-06-03 6:13 ` Philippe Mathieu-Daudé
2020-06-05 7:17 ` Gerd Hoffmann
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=17c858f1-dbd0-42b9-f2fa-22954133891a@redhat.com \
--to=thuth@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--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).