All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	kernel@pengutronix.de, patchwork-lst@pengutronix.de
Subject: Re: [PATCH v2 1/2] gpio: pca9570: Add DT bindings for NXP PCA9571
Date: Fri, 1 Jul 2022 11:19:50 +0200	[thread overview]
Message-ID: <CAMRc=MekF1V5q-pD_+yL-Ai6gd1KGKW+go0Putd9E0wbL4yahQ@mail.gmail.com> (raw)
In-Reply-To: <20220629170420.2712077-1-l.stach@pengutronix.de>

On Wed, Jun 29, 2022 at 7:04 PM Lucas Stach <l.stach@pengutronix.de> wrote:
>
> This patch adds device tree bindings for the NXP PCA9571,
> a 8-bit I2C GPIO expander.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---
>  Documentation/devicetree/bindings/gpio/gpio-pca9570.yaml | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/gpio/gpio-pca9570.yaml b/Documentation/devicetree/bindings/gpio/gpio-pca9570.yaml
> index 338c5312a106..1acaa0a3d35a 100644
> --- a/Documentation/devicetree/bindings/gpio/gpio-pca9570.yaml
> +++ b/Documentation/devicetree/bindings/gpio/gpio-pca9570.yaml
> @@ -13,6 +13,7 @@ properties:
>    compatible:
>      enum:
>        - nxp,pca9570
> +      - nxp,pca9571
>
>    reg:
>      maxItems: 1
> --
> 2.30.2
>

Applied, thanks!

Bart

      parent reply	other threads:[~2022-07-01  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 17:04 [PATCH v2 1/2] gpio: pca9570: Add DT bindings for NXP PCA9571 Lucas Stach
2022-06-29 17:04 ` [PATCH v2 2/2] gpio: pca9570: add pca9571 support Lucas Stach
2022-06-29 21:18   ` Andy Shevchenko
2022-07-01  9:20   ` Bartosz Golaszewski
2022-06-29 17:46 ` [PATCH v2 1/2] gpio: pca9570: Add DT bindings for NXP PCA9571 Krzysztof Kozlowski
2022-07-01  9:19 ` Bartosz Golaszewski [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='CAMRc=MekF1V5q-pD_+yL-Ai6gd1KGKW+go0Putd9E0wbL4yahQ@mail.gmail.com' \
    --to=brgl@bgdev.pl \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=l.stach@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=patchwork-lst@pengutronix.de \
    --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 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.