From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, clg@kaod.org, david@gibson.dropbear.id.au
Subject: [PATCH v2 0/4] ppc: valgrind "uninitialized values" fixes
Date: Wed, 30 Mar 2022 21:17:13 -0300 [thread overview]
Message-ID: <20220331001717.616938-1-danielhb413@gmail.com> (raw)
Changes from v1:
- patch 1: init 'val' union in a single statement
- all patches:
* added Philippe's R-b
* changed initialization format from {0} to { }
- v1 link: https://lists.gnu.org/archive/html/qemu-devel/2022-03/msg07234.html
Daniel Henrique Barboza (4):
target/ppc: initialize 'val' union in kvm_get_one_spr()
target/ppc: init 'lpcr' in kvmppc_enable_cap_large_decr()
target/ppc: init 'sregs' in kvmppc_put_books_sregs()
target/ppc: init 'rmmu_info' in kvm_get_radix_page_info()
target/ppc/kvm.c | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-31 0:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 0:17 Daniel Henrique Barboza [this message]
2022-03-31 0:17 ` [PATCH v2 1/4] target/ppc: initialize 'val' union in kvm_get_one_spr() Daniel Henrique Barboza
2022-03-31 1:20 ` David Gibson
2022-03-31 0:17 ` [PATCH v2 2/4] target/ppc: init 'lpcr' in kvmppc_enable_cap_large_decr() Daniel Henrique Barboza
2022-03-31 1:25 ` David Gibson
2022-03-31 17:17 ` Daniel Henrique Barboza
2022-03-31 17:36 ` Richard Henderson
2022-03-31 18:46 ` Daniel Henrique Barboza
2022-04-01 3:40 ` David Gibson
2022-04-05 19:37 ` Daniel Henrique Barboza
2022-04-01 3:38 ` David Gibson
2022-03-31 0:17 ` [PATCH v2 3/4] target/ppc: init 'sregs' in kvmppc_put_books_sregs() Daniel Henrique Barboza
2022-03-31 0:17 ` [PATCH v2 4/4] target/ppc: init 'rmmu_info' in kvm_get_radix_page_info() Daniel Henrique Barboza
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=20220331001717.616938-1-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).