From: Laurent Vivier <laurent@vivier.eu>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>
Cc: qemu-trivial@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] qom: Fix "typddef" typo
Date: Mon, 12 Oct 2020 17:24:05 +0200 [thread overview]
Message-ID: <b6d4e780-116c-af48-863c-1a65a8bc8c2d@vivier.eu> (raw)
In-Reply-To: <20201012144512.GI39408@redhat.com>
Le 12/10/2020 à 16:45, Daniel P. Berrangé a écrit :
> On Wed, Oct 07, 2020 at 06:02:55PM -0400, Eduardo Habkost wrote:
>> Fix typo introduced in the C11 #ifdef for qemu_max_align_t. It
>> never caused any problems because we always compile using
>> -std=gnu99.
>>
>> Fixes: 4c880f363e9e ("qom: Allow objects to be allocated with increased alignment")
>> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
>> ---
>> qom/object.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/qom/object.c b/qom/object.c
>> index c335dce7e4..125dabd28b 100644
>> --- a/qom/object.c
>> +++ b/qom/object.c
>> @@ -692,7 +692,7 @@ static void object_finalize(void *data)
>>
>> /* Find the minimum alignment guaranteed by the system malloc. */
>> #if __STDC_VERSION__ >= 201112L
>> -typddef max_align_t qemu_max_align_t;
>> +typedef max_align_t qemu_max_align_t;
>> #else
>
> Why do we need / have this first part of the #if at all ? We
> unconditionally add -std=gnu99, so surely this has always
> been dead code and can just be better deleted.
>
I've removed the patch from my queue.
But perhaps it will be needed in the future if we switch to a newer
standard version?
Thanks,
Laurent
next prev parent reply other threads:[~2020-10-12 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 22:02 [PATCH] qom: Fix "typddef" typo Eduardo Habkost
2020-10-08 7:01 ` Marc-André Lureau
2020-10-08 7:44 ` Philippe Mathieu-Daudé
2020-10-12 14:32 ` Laurent Vivier
2020-10-12 14:45 ` Daniel P. Berrangé
2020-10-12 15:24 ` Laurent Vivier [this message]
2020-10-13 13:16 ` Eduardo Habkost
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=b6d4e780-116c-af48-863c-1a65a8bc8c2d@vivier.eu \
--to=laurent@vivier.eu \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).