From: Markus Armbruster <armbru@redhat.com>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-devel@nongnu.org, Nicholas Piggin <npiggin@gmail.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: MAINTAINERS still leaves more files uncovered than I'd like
Date: Thu, 05 Oct 2023 15:50:35 +0200 [thread overview]
Message-ID: <87v8blxjo4.fsf@pond.sub.org> (raw)
In-Reply-To: <88854727-a895-3727-8cd9-592caa41c3fc@kaod.org> ("Cédric Le Goater"'s message of "Mon, 2 Oct 2023 13:35:48 +0200")
Cédric Le Goater <clg@kaod.org> writes:
> Regarding PPC, I am not sure where these common PPC files should go :
>
> configs/targets/ppc*
> docs/system/ppc/embedded.rst
> docs/system/target-ppc.rst
> hw/ppc/meson.build
> hw/ppc/trace*
>
> under "PowerPC TCG CPUs" may be ?
>
> These files :
>
> tests/tcg/ppc*
>
> should go under "PPC TCG target" I believe.
Suggest to check other targets for precedence you like. Preferably
well-maintained ones.
For what it's worth, Risc-V and CRIS keep it under "RISC-V TCG CPUs" and
"CRIS TCG CPUs", respectively. S390 keeps it under "S390 general
architecture support".
> I have patches for the rest.
>
> Thanks,
>
> C.
prev parent reply other threads:[~2023-10-05 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 11:43 MAINTAINERS still leaves more files uncovered than I'd like Markus Armbruster
2023-09-29 12:05 ` Cornelia Huck
2023-09-29 12:29 ` Thomas Huth
2023-09-29 14:35 ` Cornelia Huck
2023-10-02 6:18 ` Philippe Mathieu-Daudé
2023-10-02 18:25 ` Thomas Huth
2023-10-02 6:20 ` Philippe Mathieu-Daudé
2023-10-05 13:46 ` Markus Armbruster
2023-10-02 11:35 ` Cédric Le Goater
2023-10-05 13:50 ` Markus Armbruster [this message]
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=87v8blxjo4.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.