All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] dt-bindings: gpio: pca953x: Document new supported chip pca9506
Date: Mon, 18 Jan 2021 16:17:08 +0100	[thread overview]
Message-ID: <CACRpkdYj9s5mM8i9Exao+XHMj71-GH1VQ_HBYQo_7sgrvtvPtA@mail.gmail.com> (raw)
In-Reply-To: <20210115164658.187681-3-u.kleine-koenig@pengutronix.de>

On Fri, Jan 15, 2021 at 5:47 PM Uwe Kleine-König
<u.kleine-koenig@pengutronix.de> wrote:

> The previous patch added support for this chip. Add its name to the list
> of allowed compatibles.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>

Reviewed-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

  reply	other threads:[~2021-01-18 15:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 16:46 [PATCH v2 0/3] gpio: pca953x: Add support for pca9506 Uwe Kleine-König
2021-01-15 16:46 ` [PATCH v2 1/3] " Uwe Kleine-König
2021-01-15 16:46 ` [PATCH v2 2/3] dt-bindings: gpio: pca953x: Document new supported chip pca9506 Uwe Kleine-König
2021-01-18 15:17   ` Linus Walleij [this message]
2021-01-15 16:46 ` [PATCH v2 3/3] dt-bindings: gpio: pca953x: Increase allowed length for gpio-line-names Uwe Kleine-König
2021-01-18 15:17   ` Linus Walleij
2021-01-19 12:45 ` [PATCH v2 0/3] gpio: pca953x: Add support for pca9506 Bartosz Golaszewski

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=CACRpkdYj9s5mM8i9Exao+XHMj71-GH1VQ_HBYQo_7sgrvtvPtA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-gpio@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.