qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target-i386: kvm: do not initialize padding fields
Date: Thu, 18 Oct 2018 16:30:54 +0200	[thread overview]
Message-ID: <b2eae8c0-4a83-b34d-3d34-878e27de080c@redhat.com> (raw)
In-Reply-To: <CAFEAcA_6jGoD3-iTwc7=RUrYc1ac7jcjA8m26-JpRrcW+P-qRQ@mail.gmail.com>

On 18/10/2018 15:03, Peter Maydell wrote:
>  * these initializers were added by commit 7e680753cfa2
>    in order to suppress a valgrind warning
>  * they were rendered unnecessary by the later commit 076796f8fd27f4d,
>    which added the "= {}" initializer to the declaration of "events",
>    thus zero-initializing the whole struct (and so this patch does
>    not change behaviour at all)

Will do, thanks.

Paolo

      reply	other threads:[~2018-10-18 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 12:33 [Qemu-devel] [PATCH] target-i386: kvm: do not initialize padding fields Paolo Bonzini
2018-10-18 13:03 ` Peter Maydell
2018-10-18 14:30   ` Paolo Bonzini [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=b2eae8c0-4a83-b34d-3d34-878e27de080c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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).