devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Olliver Schinagl <oliver@schinagl.nl>
Subject: Re: [PATCH] leds: MAINTAINERS: include dt-bindings headers
Date: Tue, 30 Aug 2022 13:56:41 +0200	[thread overview]
Message-ID: <Yw36+cOL7alcIwQs@ada.ifak-system.com> (raw)
In-Reply-To: <20220830083625.281462-1-krzysztof.kozlowski@linaro.org>

Hei hei,

Am Tue, Aug 30, 2022 at 11:36:25AM +0300 schrieb Krzysztof Kozlowski:
> Include the Devicetree binding headers in LED SUBSYSTEM entry.

Looks like a follow-up to my yesterday's mail? ;-)

Acked-by: Alexander Dahl <ada@thorsis.com>

Greets
Alex

> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8fd6a1721e69..ebc140e71b49 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11458,6 +11458,7 @@ S:	Maintained
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git
>  F:	Documentation/devicetree/bindings/leds/
>  F:	drivers/leds/
> +F:	include/dt-bindings/leds/
>  F:	include/linux/leds.h
>  
>  LEGACY EEPROM DRIVER
> -- 
> 2.34.1
> 

  reply	other threads:[~2022-08-30 12:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  8:36 [PATCH] leds: MAINTAINERS: include dt-bindings headers Krzysztof Kozlowski
2022-08-30 11:56 ` Alexander Dahl [this message]
2022-11-25 10:52 ` Krzysztof Kozlowski
2022-11-25 11:01   ` Pavel Machek
2022-11-25 12:09     ` Krzysztof Kozlowski
2022-12-07 20:14 ` 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=Yw36+cOL7alcIwQs@ada.ifak-system.com \
    --to=ada@thorsis.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=oliver@schinagl.nl \
    --cc=pavel@ucw.cz \
    --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).