From: Anton Johansson via <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: ale@rev.ng, tsimpson@quicinc.com, bcain@quicinc.com,
mlambert@quicinc.com, babush@rev.ng, nizzo@rev.ng,
richard.henderson@linaro.org
Subject: [PATCH v9 01/12] target/hexagon: update MAINTAINERS for idef-parser
Date: Fri, 22 Apr 2022 19:40:48 +0200 [thread overview]
Message-ID: <20220422174059.4304-2-anjo@rev.ng> (raw)
In-Reply-To: <20220422174059.4304-1-anjo@rev.ng>
From: Alessandro Di Federico <ale@rev.ng>
Signed-off-by: Alessandro Di Federico <ale@rev.ng>
Signed-off-by: Anton Johansson <anjo@rev.ng>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Taylor Simpson <tsimpson@quicinc.com>
---
MAINTAINERS | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 294c88ace9..d6b62ff319 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -200,6 +200,8 @@ Hexagon TCG CPUs
M: Taylor Simpson <tsimpson@quicinc.com>
S: Supported
F: target/hexagon/
+X: target/hexagon/idef-parser/
+X: target/hexagon/gen_idef_parser_funcs.py
F: linux-user/hexagon/
F: tests/tcg/hexagon/
F: disas/hexagon.c
@@ -207,6 +209,13 @@ F: configs/targets/hexagon-linux-user/default.mak
F: docker/dockerfiles/debian-hexagon-cross.docker
F: docker/dockerfiles/debian-hexagon-cross.docker.d/build-toolchain.sh
+Hexagon idef-parser
+M: Alessandro Di Federico <ale@rev.ng>
+M: Anton Johansson <anjo@rev.ng>
+S: Supported
+F: target/hexagon/idef-parser/
+F: target/hexagon/gen_idef_parser_funcs.py
+
HPPA (PA-RISC) TCG CPUs
M: Richard Henderson <richard.henderson@linaro.org>
S: Maintained
--
2.35.1
next prev parent reply other threads:[~2022-04-22 18:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 17:40 [PATCH v9 00/12] target/hexagon: introduce idef-parser Anton Johansson via
2022-04-22 17:40 ` Anton Johansson via [this message]
2022-04-22 17:40 ` [PATCH v9 02/12] target/hexagon: import README for idef-parser Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 03/12] target/hexagon: make slot number an unsigned Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 04/12] target/hexagon: make helper functions non-static Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 05/12] target/hexagon: introduce new helper functions Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 06/12] target/hexagon: expose next PC in DisasContext Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 07/12] target/hexagon: prepare input for the idef-parser Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 08/12] target/hexagon: import flex/bison to docker files Anton Johansson via
2022-05-24 10:07 ` Alex Bennée
2022-05-25 12:29 ` Anton Johansson via
2022-05-25 15:22 ` Richard Henderson
2022-05-25 16:38 ` Alex Bennée
2022-05-25 20:14 ` Anton Johansson via
2022-05-25 20:16 ` Richard Henderson
2022-05-25 20:27 ` Anton Johansson via
2022-05-25 21:05 ` Richard Henderson
2022-04-22 17:40 ` [PATCH v9 09/12] target/hexagon: import lexer for idef-parser Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 10/12] target/hexagon: import parser " Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 11/12] target/hexagon: call idef-parser functions Anton Johansson via
2022-04-22 17:40 ` [PATCH v9 12/12] target/hexagon: import additional tests Anton Johansson via
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=20220422174059.4304-2-anjo@rev.ng \
--to=qemu-devel@nongnu.org \
--cc=ale@rev.ng \
--cc=anjo@rev.ng \
--cc=babush@rev.ng \
--cc=bcain@quicinc.com \
--cc=mlambert@quicinc.com \
--cc=nizzo@rev.ng \
--cc=richard.henderson@linaro.org \
--cc=tsimpson@quicinc.com \
/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).