From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Chris Wulff <crwulff@gmail.com>,
Marek Vasut <marex@denx.de>
Subject: Re: [PATCH] MAINTAINERS: Add the nios2 interrupt controller to the nios2 section
Date: Fri, 13 Oct 2023 11:12:23 +0200 [thread overview]
Message-ID: <01c48b28-cf80-4d10-9ecf-fb6c1d8363e2@redhat.com> (raw)
In-Reply-To: <3e159260-f1ac-d3cf-4ba4-3ce6c1b88343@linaro.org>
On 13/10/2023 10.51, Philippe Mathieu-Daudé wrote:
> On 13/10/23 08:54, Thomas Huth wrote:
>> These files obviously belong to the nios2 target, so they should
>> be listed in the nios2 section in the MAINTAINERS file.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> MAINTAINERS | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 6eecd617e0..45eb230465 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -296,7 +296,9 @@ R: Marek Vasut <marex@denx.de>
>> S: Orphan
>> F: target/nios2/
>> F: hw/nios2/
>> +F: hw/intc/nios2_vic.c
>> F: disas/nios2.c
>> +F: include/hw/intc/nios2_vic.h
>> F: configs/devices/nios2-softmmu/default.mak
>> F: tests/docker/dockerfiles/debian-nios2-cross.d/build-toolchain.sh
>> F: tests/tcg/nios2/
>
> Could we have a NiosII hardware section instead?
Is it worth the effort? ... the code is in "Orphan" state anyway...
Thomas
next prev parent reply other threads:[~2023-10-13 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 6:54 [PATCH] MAINTAINERS: Add the nios2 interrupt controller to the nios2 section Thomas Huth
2023-10-13 8:51 ` Philippe Mathieu-Daudé
2023-10-13 9:12 ` Thomas Huth [this message]
2023-10-16 21:01 ` 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=01c48b28-cf80-4d10-9ecf-fb6c1d8363e2@redhat.com \
--to=thuth@redhat.com \
--cc=crwulff@gmail.com \
--cc=marex@denx.de \
--cc=philmd@linaro.org \
--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).