From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel@nongnu.org
Cc: Eric Blake <eblake@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [Qemu-devel] [PATCH 0/3] target/xtensa: improvements for core-specific files
Date: Thu, 22 Mar 2018 11:09:37 -0700 [thread overview]
Message-ID: <20180322180940.8253-1-jcmvbkbc@gmail.com> (raw)
Hello,
this series adds .inc. to the names of non-top level xtensa core-specific
files and fixes script import_core.sh so that it does it automatically.
It also adds a fixup to the script that changes #include <xtensa-isa.h>
to #include "xtensa-isa.h".
Max Filippov (3):
target/xtensa: add .inc. to non-top level source file names
target/xtensa/import_core.sh: fix names of non-top level files
target/xtensa/import_core.sh: fix #include <xtensa-isa.h>
target/xtensa/core-dc232b.c | 4 ++--
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 +++++----
15 files changed, 14 insertions(+), 13 deletions(-)
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%)
--
2.11.0
next reply other threads:[~2018-03-22 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 18:09 Max Filippov [this message]
2018-03-22 18:09 ` [Qemu-devel] [PATCH 1/3] target/xtensa: add .inc. to non-top level source file names Max Filippov
2018-03-22 19:16 ` Eric Blake
2018-03-22 20:37 ` Max Filippov
2018-03-23 2:28 ` Philippe Mathieu-Daudé
2018-03-22 18:09 ` [Qemu-devel] [PATCH 2/3] target/xtensa/import_core.sh: fix names of non-top level files Max Filippov
2018-03-22 19:15 ` Eric Blake
2018-03-22 18:09 ` [Qemu-devel] [PATCH 3/3] target/xtensa/import_core.sh: fix #include <xtensa-isa.h> Max Filippov
2018-03-23 2:30 ` Philippe Mathieu-Daudé
2018-03-22 19:17 ` [Qemu-devel] [PATCH 0/3] target/xtensa: improvements for core-specific files Eric Blake
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=20180322180940.8253-1-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=eblake@redhat.com \
--cc=lvivier@redhat.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).