From: Conor Dooley <conor@kernel.org>
To: Nik Bune <n3q5u8@yahoo.com>
Cc: wim@linux-watchdog.org, linux@roeck-us.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
claudiu.beznea@microchip.com, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: watchdog: atmel,at91rm9200-wdt: convert txt to yaml
Date: Mon, 18 Sep 2023 18:11:34 +0100 [thread overview]
Message-ID: <20230918-5cdb7a21163283ce85a4deb5@fedora> (raw)
In-Reply-To: <20230917195520.11987-1-n3q5u8@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1558 bytes --]
On Sun, Sep 17, 2023 at 09:55:20PM +0200, Nik Bune wrote:
>
> >On Saturday, 16 September 2023 at 22:38:17 CEST, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> >
> >
> >On 16/09/2023 17:48, Nik Bune wrote:
> >
> >> Convert txt file to yaml.
> >> Add reg to the list of required properties.
> >> Add mainteiners from ./scripts/get_maintainer.pl output.
> >
> >
> >...
> >
> >> +---
> >> +$id: http://devicetree.org/schemas/watchdog/atmel,at91rm9200-wdt.yaml#
> >> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> >> +
> >> +title: Atmel AT91RM9200 System Timer Watchdog
> >> +
> >> +maintainers:
> >> + - Wim Van Sebroeck <wim@linux-watchdog.org>
> >> + - Guenter Roeck <linux@roeck-us.net
> >>
> >
> >No, these should be maintainer of device or subarch, not subsystem.
> >
>
> Is it a particular way how to determine the mainterners of the device?
>
> I have checked nearby atmel devices. They have Eugen Hristev <eugen.hristev@microchip.com> in the list of maintainers.
> Also I have found the similar patch, which looks like have never finalised, https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230525125602.640855-5-claudiu.beznea@microchip.com/
> it has
> maintainers:
> - Nicolas Ferre <nicolas.ferre@microchip.com>
> - Alexandre Belloni <alexandre.belloni@bootlin.com>
> - Claudiu Beznea <claudiu.beznea@microchip.coam>
Neither Claudiu or Eugen work at microchip any more. Nicolas should be
able to volunteer someone to look after it if you don't want to.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-09-18 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230916154826.84925-1-n3q5u8.ref@yahoo.com>
2023-09-16 15:48 ` [PATCH] dt-bindings: watchdog: atmel,at91rm9200-wdt: convert txt to yaml Nik Bune
2023-09-16 16:38 ` Rob Herring
2023-09-16 20:37 ` Krzysztof Kozlowski
2023-09-17 10:02 ` Conor Dooley
2023-09-16 20:38 ` Krzysztof Kozlowski
2023-09-17 19:35 ` Nik Bune
2023-09-18 17:09 ` Conor Dooley
2023-09-17 19:55 ` Nik Bune
2023-09-18 17:11 ` Conor Dooley [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=20230918-5cdb7a21163283ce85a4deb5@fedora \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=n3q5u8@yahoo.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.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).