From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/2] Small clean up in target/ppc/cpu.h
Date: Sun, 16 Feb 2020 22:33:54 +0100 [thread overview]
Message-ID: <cover.1581888834.git.balaton@eik.bme.hu> (raw)
Just some small clean ups to improve readability of struct CPUPPCState.
BALATON Zoltan (2):
target/ppc/cpu.h: Move fpu related members closer in cpu env
target/ppc/cpu.h: Clean up comments in the struct CPUPPCState
definition
target/ppc/cpu.h | 146 ++++++++++++++++++-----------------------------
1 file changed, 54 insertions(+), 92 deletions(-)
--
2.21.1
next reply other threads:[~2020-02-16 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-16 21:33 BALATON Zoltan [this message]
2020-02-16 21:23 ` [PATCH 1/2] target/ppc/cpu.h: Move fpu related members closer in cpu env BALATON Zoltan
2020-02-16 21:23 ` [PATCH 2/2] target/ppc/cpu.h: Clean up comments in the struct CPUPPCState definition BALATON Zoltan
2020-02-16 22:54 ` [PATCH 0/2] Small clean up in target/ppc/cpu.h David Gibson
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=cover.1581888834.git.balaton@eik.bme.hu \
--to=balaton@eik.bme.hu \
--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).