From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Harsh Prateek Bora <harshpb@linux.ibm.com>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, farosas@suse.de, npiggin@gmail.com
Subject: Re: [PATCH v3 0/2] Cleanup ppc cr get/set with helper routines
Date: Wed, 3 May 2023 11:31:41 -0300 [thread overview]
Message-ID: <3087e8d4-308f-28ef-c90e-0b1dd20f2979@gmail.com> (raw)
In-Reply-To: <20230503093619.2530487-1-harshpb@linux.ibm.com>
Queued in gitlab.com/danielhb/qemu/tree/ppc-next. Thanks,
Daniel
On 5/3/23 06:36, Harsh Prateek Bora wrote:
> This patchset introduces helper routines to get/set cr reg for better code
> readability / maintenance. No functional changes intended with this patchset.
>
> Changelog:
>
> changes from v2:
> - addressed Nick's review comments
> - holding changes from 2/4, 3/4 for future
> changes from v1:
> - addressed Fabiano's review comments
> - folding Reviewed-by tags in patch 1/4, 4/4
>
>
> *** BLURB HERE ***
>
> Harsh Prateek Bora (2):
> ppc: spapr: cleanup cr get/set with helpers.
> MAINTAINERS: Adding myself in the list for ppc/spapr
>
> MAINTAINERS | 1 +
> hw/ppc/spapr_hcall.c | 18 ++----------------
> linux-user/elfload.c | 4 +---
> linux-user/ppc/signal.c | 9 ++-------
> target/ppc/cpu.c | 17 +++++++++++++++++
> target/ppc/cpu.h | 2 ++
> target/ppc/gdbstub.c | 22 ++++------------------
> target/ppc/kvm.c | 13 ++-----------
> target/ppc/ppc-qmp-cmds.c | 6 +-----
> 9 files changed, 32 insertions(+), 60 deletions(-)
>
prev parent reply other threads:[~2023-05-03 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 9:36 [PATCH v3 0/2] Cleanup ppc cr get/set with helper routines Harsh Prateek Bora
2023-05-03 9:36 ` [PATCH v3 1/2] ppc: spapr: cleanup cr get/set with helpers Harsh Prateek Bora
2023-05-03 10:09 ` Richard Henderson
2023-05-03 20:49 ` Daniel Henrique Barboza
2023-05-04 5:33 ` Harsh Prateek Bora
2023-05-03 9:36 ` [PATCH v3 2/2] MAINTAINERS: Adding myself in the list for ppc/spapr Harsh Prateek Bora
2023-05-03 14:31 ` Daniel Henrique Barboza [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=3087e8d4-308f-28ef-c90e-0b1dd20f2979@gmail.com \
--to=danielhb413@gmail.com \
--cc=farosas@suse.de \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--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).