From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Baolin Wang <baolin.wang@linaro.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] leds: trigger: Add pattern initialization from Device Tree
Date: Wed, 12 Dec 2018 20:18:27 +0100 [thread overview]
Message-ID: <da3780eb-c4b4-5a1b-8f6d-eff1c0e98d7f@gmail.com> (raw)
In-Reply-To: <20181212121604.GA11088@amd>
On 12/12/18 1:16 PM, Pavel Machek wrote:
> On Mon 2018-12-10 22:03:18, Jacek Anaszewski wrote:
>> Hi Krzysztof,
>>
>> Thank you for the update.
>>
>> On 12/10/18 10:29 AM, Krzysztof Kozlowski wrote:
>>> Hi,
>>>
>>> I rebased on top of Jacek's patches and, as I could not find them on git kernel
>>> tree, I included them here. Also with small fixup.
>>>
>>> Changes since v1:
>>> 1. Rebase on Jacek's patches.
>>
>> Made following amendments to 2/5:
>>
>> - removed extra empty line
>> - fixed language in the commit message as proposed by Pavel
>>
>>> 2. Add patch 3/5 for fixup of Jacek's solution.
>>> 3. Drop first two patches from the series (applied).
>>> 4. Patch 5/5: Use LED_INIT_DEFAULT_TRIGGER (suggested by Jacek Anaszewski).
>>> 5. Patch 5/5: Return-on-error and log warning (suggested by Pavel Machek)
>> Applied to the for-next branch of linux-leds.git, thanks.
>>
>> Pavel - I'm still awaiting your acks, just wanted to have
>> the patch set in linux-next quicker, taking into account that
>> merge window is imminent.
>
> Ok, let me take a look. But this really should have Rob's acknowledge,
> so...
Dropped 4/5 and 5/5 as they are now superseded by v3, that appears
not to be the final too.
--
Best regards,
Jacek Anaszewski
prev parent reply other threads:[~2018-12-12 19:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 9:29 [PATCH v2 0/5] leds: trigger: Add pattern initialization from Device Tree Krzysztof Kozlowski
2018-12-10 9:29 ` [PATCH v2 1/5] led: triggers: Break the for loop after default trigger is found Krzysztof Kozlowski
2018-12-10 9:29 ` [PATCH v2 2/5] led: triggers: Add LED_INIT_DEFAULT_TRIGGER flag Krzysztof Kozlowski
2018-12-10 9:29 ` [PATCH v2 3/5] led: triggers: Initialize LED_INIT_DEFAULT_TRIGGER if trigger is brought after class Krzysztof Kozlowski
2018-12-10 9:30 ` [PATCH v2 4/5] dt-bindings: leds: Add pattern initialization from Device Tree Krzysztof Kozlowski
2018-12-11 17:23 ` Rob Herring
2018-12-12 8:42 ` Krzysztof Kozlowski
2018-12-10 9:30 ` [PATCH v2 5/5] leds: trigger: " Krzysztof Kozlowski
2018-12-10 21:03 ` [PATCH v2 0/5] " Jacek Anaszewski
2018-12-12 12:16 ` Pavel Machek
2018-12-12 19:18 ` Jacek Anaszewski [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=da3780eb-c4b4-5a1b-8f6d-eff1c0e98d7f@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=baolin.wang@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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).