From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
qemu-riscv@nongnu.org,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Alistair Francis <Alistair.Francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: [PATCH v4 0/2] riscv: Rename memmap enum constants
Date: Fri, 11 Sep 2020 13:34:45 -0400 [thread overview]
Message-ID: <20200911173447.165713-1-ehabkost@redhat.com> (raw)
Resending the enum constant rename patches from a previous QOM
cleanup series[1] separately, because of conflicts with other
sifive patches.
Series based on tags/pull-riscv-to-apply-20200910 [2]
[1] [PATCH v3 00/74] qom: Automated conversion of type checking boilerplate
https://lore.kernel.org/qemu-devel/20200825192110.3528606-1-ehabkost@redhat.com/
[2] [PULL 00/30] riscv-to-apply queue
git@github.com:alistair23/qemu.git tags/pull-riscv-to-apply-20200910
https://lore.kernel.org/qemu-devel/20200910180938.584205-1-alistair.francis@wdc.com
Based-on: 20200910180938.584205-1-alistair.francis@wdc.com
Eduardo Habkost (2):
sifive_e: Rename memmap enum constants
sifive_u: Rename memmap enum constants
include/hw/riscv/sifive_e.h | 38 ++++-----
include/hw/riscv/sifive_u.h | 34 ++++----
hw/riscv/sifive_e.c | 82 +++++++++----------
hw/riscv/sifive_u.c | 156 ++++++++++++++++++------------------
4 files changed, 155 insertions(+), 155 deletions(-)
base-commit: 9435a8b3dd35f1f926f1b9127e8a906217a5518a
prerequisite-patch-id: 8e8c13fd7650f4455348e2e12064ec3ad71833c9
prerequisite-patch-id: 2df90a089a8f5af984270b7feb259d18eb64b69e
prerequisite-patch-id: c7cbdd9cd6cc5b9f8aa9df0a7ac0c8c8693bc780
prerequisite-patch-id: 22a9a9f874d70099c7bf11e627daf5f73c8f3df9
prerequisite-patch-id: 30e7cd7cea97875ad2fbaf24e3d522243293839d
prerequisite-patch-id: a8d6dbaaaf8d35270de9c7ba6f2e8ff9d9db7a40
prerequisite-patch-id: 626a1da60314d6b18d83f64c6162890d9b287c38
prerequisite-patch-id: e478dab67068db8a25317cef162ae9531e93f8c0
prerequisite-patch-id: 0d79d052dcbcbf1b8fc115ff8ae7f9200bd16618
prerequisite-patch-id: 06d93dde5aa72136224e8812db276512184ad048
prerequisite-patch-id: d59378c76baa7765bb17aca826d14a8c69452bdf
prerequisite-patch-id: 187121ba7231bc823e4acc5941a5c9fd897f26fd
prerequisite-patch-id: df311e9276e03d8bb96144a87349ec23a6ba5b6c
prerequisite-patch-id: e706cd915562ec18efba170c769047ebe2dde54e
prerequisite-patch-id: 32a079f8fda7af4ee016e54c0a95d790cb7b9916
prerequisite-patch-id: 7b413a0fc07d717c4e5fe441e2c7b60192b4b31e
prerequisite-patch-id: 6f233317f711cbb5acae045996d12260e27ab10c
prerequisite-patch-id: 35c979882cd2400363fce562d1e028c4f2e7f934
prerequisite-patch-id: d137705ec1707ef7066908e502fcef537c59383e
prerequisite-patch-id: 13c3906d42c185c7d11e2533b8f9273e10798afa
prerequisite-patch-id: d30d7757543c9f52c54ef12d9e1a1d76edd070d2
prerequisite-patch-id: 3b22c421eaad038b2d17cfb4cc7907590080ebe1
prerequisite-patch-id: 1e6b61970a34225d00ee3e5f57630f6d3cfdbee4
prerequisite-patch-id: 1c36c766b6154fe30e076845608e6be230228c1e
prerequisite-patch-id: ccaa15790633f16dfd69aaf4885f0b3f2398658c
prerequisite-patch-id: 594fe48326a7dea997a4f4e85eb72b3549d1c8e5
prerequisite-patch-id: 2db557a303b7b99a8f8d979bf5281887f3a8162c
prerequisite-patch-id: e58aa7d72a085408bccf3ba08774eda34804548c
prerequisite-patch-id: ed0319b770df843515910350348269d6eeb4c89c
prerequisite-patch-id: 89dfbe30d51576960af2b726523d75fe9130f6c6
--
2.26.2
next reply other threads:[~2020-09-11 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 17:34 Eduardo Habkost [this message]
2020-09-11 17:34 ` [PATCH v4 1/2] sifive_e: Rename memmap enum constants Eduardo Habkost
2020-09-11 20:33 ` Alistair Francis
2020-09-11 17:34 ` [PATCH v4 2/2] sifive_u: " Eduardo Habkost
2020-09-11 20:33 ` Alistair Francis
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=20200911173447.165713-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=Alistair.Francis@wdc.com \
--cc=berrange@redhat.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).