From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marek Vasut <marex@denx.de>, devicetree@vger.kernel.org
Cc: linux-watchdog@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: [PATCH RESEND] dt-bindings: watchdog: gpio: Convert bindings to YAML
Date: Thu, 3 Nov 2022 11:29:14 -0400 [thread overview]
Message-ID: <b9fb1440-4c0c-4742-150d-3f3a83a1a952@kernel.org> (raw)
In-Reply-To: <7f8a461d-99eb-faa2-2277-dde60594cdd9@denx.de>
On 02/11/2022 18:04, Marek Vasut wrote:
> On 11/2/22 22:30, Krzysztof Kozlowski wrote:
>> On 02/11/2022 15:44, Marek Vasut wrote:
>>> Convert the gpio-wdt bindings from text to YAML ones, to permit DT validation.
>>>
>>> Signed-off-by: Marek Vasut <marex@denx.de>
>>> ---
>>> Cc: Guenter Roeck <linux@roeck-us.net>
>>> Cc: Rob Herring <robh+dt@kernel.org>
>>> Cc: Wim Van Sebroeck <wim@linux-watchdog.org>
>>> Cc: linux-watchdog@vger.kernel.org
>>> To: devicetree@vger.kernel.org
>>> ---
>>> NOTE: The Maintainer entry should likely be changed, although it seems
>>> like this driver and its matching bindings are now unmaintained.
>>
>> Please use scripts/get_maintainers.pl to get a list of necessary people
>> and lists to CC. It might happen, that command when run on an older
>> kernel, gives you outdated entries. Therefore please be sure you base
>> your patches on recent Linux kernel.
>>
>> Even if driver does not have updated maintainers entry, generic rules apply.
>
> I'm based on next-20221102, i.e. todays' next, should be recent enough.
>
> $ ./scripts/get_maintainer.pl -f drivers/watchdog/gpio_wdt.c
> Wim Van Sebroeck <wim@linux-watchdog.org> (maintainer:WATCHDOG DEVICE
> DRIVERS)
> Guenter Roeck <linux@roeck-us.net> (maintainer:WATCHDOG DEVICE DRIVERS)
> linux-watchdog@vger.kernel.org (open list:WATCHDOG DEVICE DRIVERS)
> linux-kernel@vger.kernel.org (open list)
>
> Running it against the bindings file, old or new, just adds the DT
> maintainers into the list, so not much help either. Hence the NOTE.
Yet you did not CC all DT binding maintainers, hence my reply.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-11-03 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 19:44 [PATCH RESEND] dt-bindings: watchdog: gpio: Convert bindings to YAML Marek Vasut
2022-11-02 21:30 ` Krzysztof Kozlowski
2022-11-02 22:04 ` Marek Vasut
2022-11-03 15:29 ` Krzysztof Kozlowski [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=b9fb1440-4c0c-4742-150d-3f3a83a1a952@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marex@denx.de \
--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).