From: Conor Dooley <conor@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: David Heidelberg <david@ixit.cz>,
Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Rob Herring <robh@kernel.org>,
linux-hwmon@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: arm: hwmon: gpio-fan: Convert txt bindings to yaml
Date: Tue, 12 Dec 2023 17:04:07 +0000 [thread overview]
Message-ID: <20231212-scarf-stage-0f3c6947c1bb@spud> (raw)
In-Reply-To: <b327d7e4-35fb-4b1e-bde2-267bba918df6@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Mon, Dec 11, 2023 at 11:42:09AM -0800, Guenter Roeck wrote:
> On 12/11/23 11:28, David Heidelberg wrote:
> > Nothing, as I was working on others ARM-related bindings, it just sneaked in. Good catch.
> >
> > Should I resend with adjusted name or can this by done by quick adjust before the merge?
> >
>
> No need to resend. I'll fix that up, assuming you get a Reviewed-by: tag from a dt
> maintainer.
I think it is okay.
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-12 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 17:15 [PATCH v4 1/3] dt-bindings: arm: hwmon: gpio-fan: Convert txt bindings to yaml David Heidelberg
2023-12-09 17:15 ` [PATCH v4 2/3] arm64: dts: rockchip: make dts use gpio-fan matrix instead of array David Heidelberg
2023-12-09 17:15 ` [PATCH v4 3/3] ARM: dts: tegra30-ouya: " David Heidelberg
2023-12-11 14:34 ` [PATCH v4 1/3] dt-bindings: arm: hwmon: gpio-fan: Convert txt bindings to yaml Guenter Roeck
2023-12-11 19:28 ` David Heidelberg
2023-12-11 19:42 ` Guenter Roeck
2023-12-12 17:04 ` Conor Dooley [this message]
2023-12-12 20:16 ` (subset) " Heiko Stuebner
2023-12-12 20:53 ` Guenter Roeck
2023-12-14 16:25 ` (subset) " Thierry Reding
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=20231212-scarf-stage-0f3c6947c1bb@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--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 \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.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