From: Eric Blake <eblake@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, mark.cave-ayland@ilande.co.uk,
alex.bennee@linaro.org, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 2/2] configure: Use quotes around uses of $CPU_CFLAGS
Date: Thu, 2 May 2019 01:49:19 -0500 [thread overview]
Message-ID: <9e4a2f00-7652-c1dc-e45e-7407810ce4d2@redhat.com> (raw)
In-Reply-To: <20190501223819.8584-3-richard.henderson@linaro.org>
On 5/1/19 5:38 PM, Richard Henderson wrote:
> About half of the values to which CPU_CFLAGS is set
> have multiple space separated arguments.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> configure | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/configure b/configure
> index 234cb929ca..16bd4375d1 100755
> --- a/configure
> +++ b/configure
> @@ -1543,37 +1543,37 @@ case "$cpu" in
> CPU_CFLAGS="-m64"
> LDFLAGS="-m64 $LDFLAGS"
> cross_cc_ppc64=$cc
> - cross_cc_cflags_ppc64=$CPU_CFLAGS
> + cross_cc_cflags_ppc64="$CPU_CFLAGS"
Makes no difference semantically (bare variable assignments are not
subject to word splitting or globbing, so the quotes don't change the
result); the only reason to change this is for consistency (using quotes
everywhere is easier to remember, whether or not they are in a context
that matter).
So I'm okay whether this patch goes in or is omitted.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <eblake@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: alex.bennee@linaro.org, mark.cave-ayland@ilande.co.uk,
qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH 2/2] configure: Use quotes around uses of $CPU_CFLAGS
Date: Thu, 2 May 2019 01:49:19 -0500 [thread overview]
Message-ID: <9e4a2f00-7652-c1dc-e45e-7407810ce4d2@redhat.com> (raw)
Message-ID: <20190502064919.brwc1WqZPabV5MwD2vKbbo6dKoWLCpdr_xNTySMsA8c@z> (raw)
In-Reply-To: <20190501223819.8584-3-richard.henderson@linaro.org>
On 5/1/19 5:38 PM, Richard Henderson wrote:
> About half of the values to which CPU_CFLAGS is set
> have multiple space separated arguments.
>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> configure | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/configure b/configure
> index 234cb929ca..16bd4375d1 100755
> --- a/configure
> +++ b/configure
> @@ -1543,37 +1543,37 @@ case "$cpu" in
> CPU_CFLAGS="-m64"
> LDFLAGS="-m64 $LDFLAGS"
> cross_cc_ppc64=$cc
> - cross_cc_cflags_ppc64=$CPU_CFLAGS
> + cross_cc_cflags_ppc64="$CPU_CFLAGS"
Makes no difference semantically (bare variable assignments are not
subject to word splitting or globbing, so the quotes don't change the
result); the only reason to change this is for consistency (using quotes
everywhere is easier to remember, whether or not they are in a context
that matter).
So I'm okay whether this patch goes in or is omitted.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-05-02 6:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 22:38 [Qemu-devel] [PATCH 0/2] configure: Fix make check-tcg for ppc64le Richard Henderson
2019-05-01 22:38 ` Richard Henderson
2019-05-01 22:38 ` [Qemu-devel] [PATCH 1/2] configure: Distinguish ppc64 and ppc64le hosts Richard Henderson
2019-05-01 22:38 ` Richard Henderson
2019-05-01 22:38 ` [Qemu-devel] [PATCH 2/2] configure: Use quotes around uses of $CPU_CFLAGS Richard Henderson
2019-05-01 22:38 ` Richard Henderson
2019-05-02 6:25 ` Philippe Mathieu-Daudé
2019-05-02 6:25 ` Philippe Mathieu-Daudé
2019-05-02 6:49 ` Eric Blake [this message]
2019-05-02 6:49 ` Eric Blake
2019-05-02 4:04 ` [Qemu-devel] [PATCH 0/2] configure: Fix make check-tcg for ppc64le David Gibson
2019-05-02 4:04 ` David Gibson
2019-05-02 4:59 ` Richard Henderson
2019-05-02 4:59 ` Richard Henderson
2019-05-02 10:47 ` Alex Bennée
2019-05-02 10:47 ` Alex Bennée
2019-05-02 15:14 ` Richard Henderson
2019-05-02 15:14 ` Richard Henderson
2019-05-02 15:22 ` Alex Bennée
2019-05-02 15:22 ` Alex Bennée
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=9e4a2f00-7652-c1dc-e45e-7407810ce4d2@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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).