Linux-LEDs Archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Patrick Rudolph <patrick.rudolph@9elements.com>,
	 linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>
Subject: Re: [PATCH v1 0/4] leds: max5970: Allow to use on non-OF platforms
Date: Thu, 21 Dec 2023 14:44:00 +0000	[thread overview]
Message-ID: <170316984054.602239.8396148878635955139.b4-ty@kernel.org> (raw)
In-Reply-To: <20231214184050.1272848-1-andriy.shevchenko@linux.intel.com>

On Thu, 14 Dec 2023 20:40:07 +0200, Andy Shevchenko wrote:
> Allow to use driver on non-OF platforms and other cleanups.
> 
> Andy Shevchenko (4):
>   leds: max5970: Remove unused variable
>   leds: max5970: Make use of device properties
>   leds: max5970: Make use of dev_err_probe()
>   leds: max5970: Add missing headers
> 
> [...]

Applied, thanks!

[1/4] leds: max5970: Remove unused variable
      commit: d3578b4982e6ebccbd898806ac86b2db4b2bcc5e
[2/4] leds: max5970: Make use of device properties
      commit: 6d63d05e26f8d5e22308efc25793660101fd7602
[3/4] leds: max5970: Make use of dev_err_probe()
      commit: e7baa5b437a782308b86c1517ae252fd1353eb0b
[4/4] leds: max5970: Add missing headers
      commit: 808c7881876756dfcd8c4d0c3efc27c9262da822

--
Lee Jones [李琼斯]


      parent reply	other threads:[~2023-12-21 14:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 18:40 [PATCH v1 0/4] leds: max5970: Allow to use on non-OF platforms Andy Shevchenko
2023-12-14 18:40 ` [PATCH v1 1/4] leds: max5970: Remove unused variable Andy Shevchenko
2023-12-14 18:40 ` [PATCH v1 2/4] leds: max5970: Make use of device properties Andy Shevchenko
2023-12-14 18:40 ` [PATCH v1 3/4] leds: max5970: Make use of dev_err_probe() Andy Shevchenko
2023-12-14 18:40 ` [PATCH v1 4/4] leds: max5970: Add missing headers Andy Shevchenko
2023-12-21 14:44 ` Lee Jones [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=170316984054.602239.8396148878635955139.b4-ty@kernel.org \
    --to=lee@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=patrick.rudolph@9elements.com \
    --cc=pavel@ucw.cz \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).