From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: imammedo@redhat.com, thuth@redhat.com, agraf@suse.de,
david@gibson.dropbear.id.au, John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] ppc: remove dead definitions
Date: Tue, 19 Sep 2017 17:36:09 -0400 [thread overview]
Message-ID: <20170919213611.8988-1-jsnow@redhat.com> (raw)
Following conversation from:
https://lists.gnu.org/archive/html/qemu-devel/2017-09/msg05362.html
Split into two patches:
(1) Definitions that match Igor's cleanup precisely
(2) Everything else I brazenly took a chainsaw to with little precision
(Only lightly tested.)
John Snow (2):
ppc: remove unused CPU definitions
ppc: remove all unused CPU definitions
target/ppc/cpu-models.h | 255 ------------------------------------------------
1 file changed, 255 deletions(-)
--
2.9.5
next reply other threads:[~2017-09-19 21:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 21:36 John Snow [this message]
2017-09-19 21:36 ` [Qemu-devel] [PATCH 1/2] ppc: remove unused CPU definitions John Snow
2017-09-20 18:47 ` Thomas Huth
2017-09-23 5:23 ` David Gibson
2017-09-19 21:36 ` [Qemu-devel] [PATCH 2/2] ppc: remove all " John Snow
2017-09-20 18:52 ` Thomas Huth
2017-09-23 5:28 ` 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=20170919213611.8988-1-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).