qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: Radoslaw Biernacki <rad@semihalf.com>,
	Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org,
	QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [PATCH] MAINTAINERS: Add some unowned files to the SBSA-REF section
Date: Thu, 5 Oct 2023 16:31:50 +0200	[thread overview]
Message-ID: <454b4732-d9ce-3cc5-e018-8fe2f88cc406@redhat.com> (raw)
In-Reply-To: <ZRb3aTLxBSnVGGr2@qc-i7.hemma.eciton.net>

On 29/09/2023 18.12, Leif Lindholm wrote:
> On Fri, Sep 29, 2023 at 16:19:18 +0200, Thomas Huth wrote:
>> These files belong to the sbsa-ref machine and thus should
>> be listed here.
> 
> First of all, thanks for this.
> 
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>   MAINTAINERS | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 874234cb7b..fc415d3cea 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -954,6 +954,9 @@ R: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
>>   L: qemu-arm@nongnu.org
>>   S: Maintained
>>   F: hw/arm/sbsa-ref.c
>> +F: hw/misc/sbsa_ec.c
> 
> Yes, pure oversight, sorry about that.
> 
>> +F: hw/watchdog/sbsa_gwdt.c
>> +F: include/hw/watchdog/sbsa_gwdt.h
> 
> I just want to clarify that this is not "the watchdog for the SBSA
> platform", but "the watchdog defined by Arm's SBSA specification"
> (and belatedly the BSA specification)" - the specification that
> sbsa-ref (intends to) provide a compliant platform implementation for.

Thanks for the clarification!

> Another such component is the "generic UART", but since that is a
> subset of pl011 there is no real value in providing a dedicated model
> of it.
> 
> Which I guess is a long-winded way of saying: this component does not
> necessarily want/need the same maintainers as the sbsa-ref platform.
> I'm still happy to maintain it, and it may make sense to keep it under
> this header for now.

I think as long as the sbsa-ref machine is the only one in our git tree that 
uses this device, it's fine if we add the sbsa watchdog to this section 
here. If there will ever be another machine that uses this device, we can 
still reconsider and create a dedicated section for it in the MAINTAINERS 
file if necessary.

> (In which case
> Reviewed-by: Leif Lindholm <quic_llindhol@quicinc.com>
> )

  Thanks!
   Thomas




  reply	other threads:[~2023-10-05 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 14:19 [PATCH] MAINTAINERS: Add some unowned files to the SBSA-REF section Thomas Huth
2023-09-29 16:12 ` Leif Lindholm
2023-10-05 14:31   ` Thomas Huth [this message]
2023-10-05 13:57 ` Markus Armbruster
2023-10-06  6:41 ` 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=454b4732-d9ce-3cc5-e018-8fe2f88cc406@redhat.com \
    --to=thuth@redhat.com \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=quic_llindhol@quicinc.com \
    --cc=rad@semihalf.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).