devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org,
	Rob Herring <robh+dt@kernel.org>,
	Wim Van Sebroeck <wim@linux-watchdog.org>
Subject: Re: [PATCH v2] dt-bindings: watchdog: gpio: Convert bindings to YAML
Date: Thu, 3 Nov 2022 17:31:12 +0100	[thread overview]
Message-ID: <a7db27cb-bb50-ed13-f2b7-54a8f66b1b97@denx.de> (raw)
In-Reply-To: <20221103012205.GA2109899@roeck-us.net>

On 11/3/22 02:22, Guenter Roeck wrote:
> On Wed, Nov 02, 2022 at 11:05:30PM +0100, 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
>> ---
>> V2: - Add missing required: properties
>>      - Drop quotes around ref: referenced schema file name
>> ---
>> NOTE: The Maintainer entry should likely be changed, although it seems
>>        like this driver and its matching bindings are now unmaintained.
> 
> I still can not parse this note. The MAINTAINERS entry for watchdog devices
> includes
> 
> F:      Documentation/devicetree/bindings/watchdog/
> F:      drivers/watchdog/
> 
> which should cover both the old and the new bindings as well as the driver.
> 
> Please explain.

I don't mind placing you and Wim into the yaml DT maintainer section if 
that's OK with you ?

  reply	other threads:[~2022-11-03 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03  1:22 [PATCH v2] dt-bindings: watchdog: gpio: Convert bindings to YAML Guenter Roeck
2022-11-03 16:31 ` Marek Vasut [this message]
2022-11-03 17:20   ` Guenter Roeck
2022-11-03 17:29     ` Marek Vasut
  -- strict thread matches above, loose matches on Subject: below --
2022-11-03  1:27 Guenter Roeck
2022-11-02 22:05 Marek Vasut
2022-11-04 21:57 ` Rob Herring

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=a7db27cb-bb50-ed13-f2b7-54a8f66b1b97@denx.de \
    --to=marex@denx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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).