From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [Qemu-devel] [PULL 0/4] target/xtensa fixes for 2.12
Date: Mon, 26 Mar 2018 14:44:09 -0700 [thread overview]
Message-ID: <20180326214409.15326-1-jcmvbkbc@gmail.com> (raw)
Hi Peter,
please pull the following fixes for target/xtensa for 2.12:
The following changes since commit 7b93d78a04aa242d377ae213b79db6c319c71847:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2018-03-26 15:17:25 +0100)
are available in the git repository at:
git://github.com/OSLL/qemu-xtensa.git tags/20180326-xtensa
for you to fetch changes up to d0ce7e9cfc8eda113f872b608fe4a3dd7662997e:
target/xtensa: fix timers test (2018-03-26 14:17:04 -0700)
----------------------------------------------------------------
target/xtensa fixes for 2.12:
- add .inc. to non-top level source file names under target/xtensa;
- fix #include <xtensa-isa.h> in the import_core.sh script;
- remove stray linux-user/xtensa/syscall.h;
- fix timers test.
----------------------------------------------------------------
Max Filippov (4):
target/xtensa: add .inc. to non-top level source file names
target/xtensa/import_core.sh: fix #include <xtensa-isa.h>
linux-user/xtensa: remove stray syscall.h
target/xtensa: fix timers test
linux-user/xtensa/syscall.h | 0
target/xtensa/core-dc232b.c | 6 +++---
target/xtensa/core-dc232b/{gdb-config.c => gdb-config.inc.c} | 0
.../core-dc232b/{xtensa-modules.c => xtensa-modules.inc.c} | 0
target/xtensa/core-dc233c.c | 4 ++--
target/xtensa/core-dc233c/{gdb-config.c => gdb-config.inc.c} | 0
.../core-dc233c/{xtensa-modules.c => xtensa-modules.inc.c} | 0
target/xtensa/core-de212.c | 4 ++--
target/xtensa/core-de212/{gdb-config.c => gdb-config.inc.c} | 0
.../xtensa/core-de212/{xtensa-modules.c => xtensa-modules.inc.c} | 0
target/xtensa/core-fsf.c | 2 +-
.../xtensa/core-fsf/{xtensa-modules.c => xtensa-modules.inc.c} | 0
target/xtensa/core-sample_controller.c | 4 ++--
.../core-sample_controller/{gdb-config.c => gdb-config.inc.c} | 0
.../{xtensa-modules.c => xtensa-modules.inc.c} | 0
target/xtensa/import_core.sh | 9 +++++----
tests/tcg/xtensa/Makefile | 2 +-
17 files changed, 16 insertions(+), 15 deletions(-)
delete mode 100644 linux-user/xtensa/syscall.h
rename target/xtensa/core-dc232b/{gdb-config.c => gdb-config.inc.c} (100%)
rename target/xtensa/core-dc232b/{xtensa-modules.c => xtensa-modules.inc.c} (100%)
rename target/xtensa/core-dc233c/{gdb-config.c => gdb-config.inc.c} (100%)
rename target/xtensa/core-dc233c/{xtensa-modules.c => xtensa-modules.inc.c} (100%)
rename target/xtensa/core-de212/{gdb-config.c => gdb-config.inc.c} (100%)
rename target/xtensa/core-de212/{xtensa-modules.c => xtensa-modules.inc.c} (100%)
rename target/xtensa/core-fsf/{xtensa-modules.c => xtensa-modules.inc.c} (100%)
rename target/xtensa/core-sample_controller/{gdb-config.c => gdb-config.inc.c} (100%)
rename target/xtensa/core-sample_controller/{xtensa-modules.c => xtensa-modules.inc.c} (100%)
--
Thanks.
-- Max
next reply other threads:[~2018-03-26 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 21:44 Max Filippov [this message]
2018-03-27 15:24 ` [Qemu-devel] [PULL 0/4] target/xtensa fixes for 2.12 Peter Maydell
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=20180326214409.15326-1-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=peter.maydell@linaro.org \
--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).