From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Brian Cain" <bcain@quicinc.com>,
qemu-trivial@nongnu.org, "Anton Johansson" <anjo@rev.ng>,
"Alessandro Di Federico" <ale@rev.ng>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH 0/2] misc: Rename included template headers using '.inc' suffix
Date: Tue, 10 Sep 2024 13:28:31 +0200 [thread overview]
Message-ID: <20240910112833.27594-1-philmd@linaro.org> (raw)
Follow Coding Style:
If you do use template header files they should be named with
the ``.c.inc`` or ``.h.inc`` suffix to make it clear they are
being included for expansion.
Philippe Mathieu-Daudé (2):
target/hexagon: Rename macros.inc -> macros.h.inc
tests/bench: Rename test_akcipher_keys.inc -> test_akcipher_keys.c.inc
target/hexagon/idef-parser/README.rst | 4 ++--
target/hexagon/idef-parser/{macros.inc => macros.h.inc} | 0
tests/bench/benchmark-crypto-akcipher.c | 2 +-
.../{test_akcipher_keys.inc => test_akcipher_keys.c.inc} | 0
target/hexagon/gen_idef_parser_funcs.py | 2 +-
target/hexagon/meson.build | 2 +-
6 files changed, 5 insertions(+), 5 deletions(-)
rename target/hexagon/idef-parser/{macros.inc => macros.h.inc} (100%)
rename tests/bench/{test_akcipher_keys.inc => test_akcipher_keys.c.inc} (100%)
--
2.45.2
next reply other threads:[~2024-09-10 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 11:28 Philippe Mathieu-Daudé [this message]
2024-09-10 11:28 ` [PATCH 1/2] target/hexagon: Rename macros.inc -> macros.h.inc Philippe Mathieu-Daudé
2024-09-10 13:53 ` Brian Cain
2024-09-10 14:21 ` Anton Johansson via
2024-09-10 11:28 ` [PATCH 2/2] tests/bench: Rename test_akcipher_keys.inc -> test_akcipher_keys.c.inc Philippe Mathieu-Daudé
2024-09-10 19:18 ` [PATCH 0/2] misc: Rename included template headers using '.inc' suffix Richard Henderson
2024-09-20 7:09 ` 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=20240910112833.27594-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=bcain@quicinc.com \
--cc=berrange@redhat.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).