From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel@nongnu.org
Cc: Max Filippov <jcmvbkbc@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: [Qemu-devel] [PULL] target-xtensa queue
Date: Tue, 15 Oct 2013 17:38:17 +0400 [thread overview]
Message-ID: <1381844297-1728-1-git-send-email-jcmvbkbc@gmail.com> (raw)
Hello Antony,
Please pull my current target-xtensa patch queue.
There's a single patch implementing in_asm logging.
The following changes since commit 1680d485777ecf436d724631ea8722cc0c66990e:
Merge remote-tracking branch 'rth/tcg-ldst-6' into staging (2013-10-14 09:59:59 -0700)
are available in the git repository at:
git://github.com/OSLL/qemu-xtensa.git tags/20131015-xtensa
for you to fetch changes up to ca529f8e13557cc2feb2eee3872d422712d9bcb0:
target-xtensa: add in_asm logging (2013-10-15 17:23:46 +0400)
----------------------------------------------------------------
xtensa queue 2013-10-15
----------------------------------------------------------------
Max Filippov (1):
target-xtensa: add in_asm logging
target-xtensa/translate.c | 8 ++++++++
1 file changed, 8 insertions(+)
--
1.8.1.4
reply other threads:[~2013-10-15 13:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1381844297-1728-1-git-send-email-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@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).