From: Rob Herring <robh@kernel.org>
To: Vincent Knecht <vincent.knecht@mailoo.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
phone-devel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
hns@goldelico.com, Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 01/12] dt-bindings: leds: Convert is31fl319x to dtschema
Date: Thu, 21 Jul 2022 11:14:21 -0600 [thread overview]
Message-ID: <20220721171421.GA1583139-robh@kernel.org> (raw)
In-Reply-To: <20220712100841.1538395-2-vincent.knecht@mailoo.org>
On Tue, 12 Jul 2022 12:08:27 +0200, Vincent Knecht wrote:
> Convert leds-is31fl319x.txt to dtschema.
> Set license to the one recommended by DT project
> and set myself as maintainer.
>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Vincent Knecht <vincent.knecht@mailoo.org>
> ---
> v3:
> - changed license back to (GPL-2.0-only OR BSD-2-Clause) and
> maintainer to myself, with Nikolaus agreement
> ---
> .../bindings/leds/issi,is31fl319x.yaml | 113 ++++++++++++++++++
> .../bindings/leds/leds-is31fl319x.txt | 61 ----------
> 2 files changed, 113 insertions(+), 61 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/leds/issi,is31fl319x.yaml
> delete mode 100644 Documentation/devicetree/bindings/leds/leds-is31fl319x.txt
>
Applied, thanks!
next prev parent reply other threads:[~2022-07-21 17:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 10:08 [PATCH v5 00/12] leds: Fix/Add is31fl319{0,1,3} support Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 01/12] dt-bindings: leds: Convert is31fl319x to dtschema Vincent Knecht
2022-07-21 17:14 ` Rob Herring [this message]
2022-07-12 10:08 ` [PATCH v5 02/12] dt-bindings: leds: is31fl319x: Document variants specificities Vincent Knecht
2022-07-21 17:14 ` Rob Herring
2022-07-12 10:08 ` [PATCH v5 03/12] leds: is31fl319x: Add missing si-en compatibles Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 04/12] leds: is31fl319x: Use non-wildcard names for vars, structs and defines Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 05/12] leds: is31fl319x: Move chipset-specific values in chipdef struct Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 06/12] leds: is31fl319x: Add support for is31fl319{0,1,3} chips Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 07/12] leds: is31fl319x: Cleanup formatting and dev_dbg calls Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 08/12] leds: is31fl319x: Make use of device properties Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 09/12] leds: is31fl319x: Make use of dev_err_probe() Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 10/12] leds: is31fl319x: Fix devm vs. non-devm ordering Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 11/12] leds: is31fl319x: use simple i2c probe function Vincent Knecht
2022-07-12 10:08 ` [PATCH v5 12/12] leds: is31fl319x: sort header inclusion alphabetically Vincent Knecht
2022-07-31 17:21 ` [PATCH v5 00/12] leds: Fix/Add is31fl319{0,1,3} support Vincent Knecht
2022-08-02 14:44 ` 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=20220721171421.GA1583139-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vincent.knecht@mailoo.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 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).