From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Remove blanks before \n in output strings
Date: Mon, 12 Sep 2011 21:48:00 +0100 [thread overview]
Message-ID: <CAFEAcA8sNycdTkuL=cWDq9zmj5ZTKMLzkZPN36cLSYEEz4t5uQ@mail.gmail.com> (raw)
In-Reply-To: <1315859581-27703-1-git-send-email-weil@mail.berlios.de>
On 12 September 2011 21:33, Stefan Weil <weil@mail.berlios.de> wrote:
> Those blanks violate the coding conventions, see
> scripts/checkpatch.pl.
I can see doing this if there are any cases of actual
output-to-users here, but for debug printfs, it scarcely
seems worth the effort. I'm not arguing against this particular
patch, since you've done the work now; just wondering what the
motivation was...
> diff --git a/tests/test-i386.c b/tests/test-i386.c
> index 9cb5b51..8e64bba 100644
> --- a/tests/test-i386.c
> +++ b/tests/test-i386.c
> @@ -802,7 +802,7 @@ void test_fcmp(double a, double b)
> "fstsw %%ax\n"
> : "=a" (fpus)
> : "t" (a), "u" (b));
> - printf("fcom(%f %f)=%04lx \n",
> + printf("fcom(%f %f)=%04lx\n",
> a, b, fpus & (0x4500 | FPUS_EMASK));
> fpu_clear_exceptions();
> asm("fucom %2\n"
(To save anybody else checking) Changing the output of this test
program is OK because tests/Makefile makes the arguable assumption
that we're running on an x86 box and can regenerate the "known good"
output reference rather than having to keep a copy in git...
thanks
-- PMM
next prev parent reply other threads:[~2011-09-12 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 20:33 [Qemu-devel] [PATCH] Remove blanks before \n in output strings Stefan Weil
2011-09-12 20:48 ` Peter Maydell [this message]
2011-09-16 14:44 ` Anthony Liguori
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='CAFEAcA8sNycdTkuL=cWDq9zmj5ZTKMLzkZPN36cLSYEEz4t5uQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).