From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, edgari@xilinx.com,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH microblaze v1 0/6] Microblaze Cleanups
Date: Mon, 27 Apr 2015 17:47:06 +0300 [thread overview]
Message-ID: <553E4BEA.2070403@msgid.tls.msk.ru> (raw)
In-Reply-To: <1430075424-25975-1-git-send-email-crosthwaite.peter@gmail.com>
26.04.2015 22:10, Peter Crosthwaite wrote:
> Hi Edgar,
>
> This is some code cleanup of Microblaze. Mainly unused code
> deletion but also code share of the defconfig (P1).
Applied all 6 to -trivial, as is, since the whole series
does not perform any code changes. Renumbering EXCP_*
constants can be done later.
Thanks,
/mjt
next prev parent reply other threads:[~2015-04-27 14:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 19:10 [Qemu-devel] [PATCH microblaze v1 0/6] Microblaze Cleanups Peter Crosthwaite
2015-04-26 19:10 ` [Qemu-devel] [PATCH microblaze v1 1/6] defconfigs: Piggyback microblazeel on microblaze Peter Crosthwaite
2015-04-26 19:10 ` [Qemu-devel] [PATCH microblaze v1 2/6] mb: mmu: Delete flip_um fn prototype Peter Crosthwaite
2015-04-26 19:10 ` [Qemu-devel] [PATCH microblaze v1 3/6] mb: cpu: Remote unused cpu_get_pc Peter Crosthwaite
2015-04-30 8:43 ` Alex Bennée
2015-04-26 19:10 ` [Qemu-devel] [PATCH microblaze v1 4/6] mb: cpu: Remove unused CC_OP enum Peter Crosthwaite
2015-04-26 19:10 ` [Qemu-devel] [PATCH microblaze v1 5/6] mb: cpu: Delete EXCP_NMI Peter Crosthwaite
2015-04-27 9:28 ` Edgar E. Iglesias
2015-04-27 13:41 ` Michael Tokarev
2015-04-27 14:13 ` Peter Crosthwaite
2015-04-27 23:25 ` Edgar E. Iglesias
2015-04-26 19:10 ` [Qemu-devel] [PATCH microblaze v1 6/6] mb: cpu: delete unused cpu_interrupts_enabled Peter Crosthwaite
2015-04-27 14:47 ` Michael Tokarev [this message]
2015-04-29 5:46 ` [Qemu-devel] [PATCH microblaze v1 0/6] Microblaze Cleanups Michael Tokarev
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=553E4BEA.2070403@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=crosthwaite.peter@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=edgari@xilinx.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).