All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Markuss Broks <markuss.broks@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
	phone-devel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Pavel Machek <pavel@ucw.cz>,
	~postmarketos/upstreaming@lists.sr.ht,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: leds: convert ktd2692 bindings to yaml
Date: Fri, 8 Apr 2022 15:59:39 -0500	[thread overview]
Message-ID: <YlCiO3hfTtzJwq5H@robh.at.kernel.org> (raw)
In-Reply-To: <20220408184104.13665-2-markuss.broks@gmail.com>

On Fri, 08 Apr 2022 21:40:54 +0300, Markuss Broks wrote:
> This patch converts the leds-ktd2692.txt bindings to modern yaml
> style device-tree bindings.
> 
> Signed-off-by: Markuss Broks <markuss.broks@gmail.com>
> ---
>  .../bindings/leds/kinetic,ktd2692.yaml        | 87 +++++++++++++++++++
>  .../devicetree/bindings/leds/leds-ktd2692.txt | 50 -----------
>  2 files changed, 87 insertions(+), 50 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/leds/kinetic,ktd2692.yaml
>  delete mode 100644 Documentation/devicetree/bindings/leds/leds-ktd2692.txt
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-04-08 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 18:40 [PATCH v6 0/2] Make AUX gpio pin optional for ktd2692 Markuss Broks
2022-04-08 18:40 ` [PATCH v6 1/2] dt-bindings: leds: convert ktd2692 bindings to yaml Markuss Broks
2022-04-08 20:59   ` Rob Herring [this message]
2022-04-08 18:40 ` [PATCH v6 2/2] leds: ktd2692: Make aux-gpios optional Markuss Broks
2022-04-11 17:11   ` Andy Shevchenko
2022-05-04 17:24     ` Pavel Machek

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=YlCiO3hfTtzJwq5H@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=devicetree@vger.kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=markuss.broks@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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.