From: Rob Herring <robh@kernel.org>
To: Marcel Ziswiler <marcel@ziswiler.com>
Cc: devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Marek Vasut <marek.vasut@gmail.com>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v1 02/14] dt-bindings: gpio: fix gpio-hog example
Date: Tue, 11 Jan 2022 19:58:13 -0600 [thread overview]
Message-ID: <Yd41tcVzxDjk+151@robh.at.kernel.org> (raw)
In-Reply-To: <20220107180314.1816515-3-marcel@ziswiler.com>
On Fri, 07 Jan 2022 19:03:02 +0100, Marcel Ziswiler wrote:
> From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
>
> Even if this is no yaml yet at least fix the example to be compliant to
> later schema as e.g. found in gpio-pca95xx.yaml, fairchild,74hc595.yaml
> and gpio/fsl-imx-gpio.yaml.
>
> Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> ---
>
> Documentation/devicetree/bindings/gpio/gpio.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-01-12 1:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 18:03 [PATCH v1 00/14] arm64: prepare and add verdin imx8m mini support Marcel Ziswiler
2022-01-07 18:03 ` [PATCH v1 01/14] arm64: dts: imx8mm: fix strange hex notation Marcel Ziswiler
2022-01-10 23:58 ` Laurent Pinchart
2022-01-07 18:03 ` [PATCH v1 02/14] dt-bindings: gpio: fix gpio-hog example Marcel Ziswiler
2022-01-12 1:58 ` Rob Herring [this message]
2022-01-07 18:03 ` [PATCH v1 13/14] dt-bindings: arm: fsl: add toradex,verdin-imx8mm et al Marcel Ziswiler
2022-01-12 1:58 ` Rob Herring
2022-01-07 18:03 ` [PATCH v1 14/14] arm64: dts: freescale: add initial support for verdin imx8m mini Marcel Ziswiler
2022-01-10 8:47 ` Krzysztof Kozlowski
2022-01-14 13:28 ` Marcel Ziswiler
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=Yd41tcVzxDjk+151@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marcel@ziswiler.com \
--cc=marek.vasut@gmail.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).