From: Rob Herring <robh@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, peiyu li <579lpy@gmail.com>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] dt-bindings: hwmon: convert lm87 and max6650 to dtschema
Date: Thu, 21 Mar 2024 11:48:59 -0500 [thread overview]
Message-ID: <20240321164859.GA2085432-robh@kernel.org> (raw)
In-Reply-To: <20240321-hwmon_yaml-v2-0-74fa8eb60ec9@gmail.com>
On Thu, Mar 21, 2024 at 05:33:16PM +0100, Javier Carrasco wrote:
> This series converts the existing lm87.txt and max6650.txt bindings to
> dtschema. Both are direct conversions with no additional properties.
>
> There has been an attempt to convert the bindings of the lm87 before
> [1], but the author (added to recipients) has confirmed that no further
> versions will be submitted, and no acknowledgment is desired.
>
> Link: https://lore.kernel.org/linux-hwmon/20231030125221.12974-1-579lpy@gmail.com [1]
>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> ---
> Changes in v2:
> - max6650: add property constraints and commit message indentation.
> - lm87: No changes, already applied to hwmon-next.
Then you should not have sent it again. And you forgot Conor's
Reviewed-by.
Rob
prev parent reply other threads:[~2024-03-21 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 16:33 [PATCH v2 0/2] dt-bindings: hwmon: convert lm87 and max6650 to dtschema Javier Carrasco
2024-03-21 16:33 ` [PATCH v2 1/2] dt-bindings: hwmon: lm87: convert " Javier Carrasco
2024-03-21 17:46 ` Krzysztof Kozlowski
2024-03-21 17:47 ` Krzysztof Kozlowski
2024-03-21 16:33 ` [PATCH v2 2/2] dt-bindings: hwmon: max6650: " Javier Carrasco
2024-03-21 16:50 ` Rob Herring
2024-03-23 14:15 ` Guenter Roeck
2024-03-21 16:48 ` Rob Herring [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=20240321164859.GA2085432-robh@kernel.org \
--to=robh@kernel.org \
--cc=579lpy@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jdelvare@suse.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.