From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-leds@vger.kernel.org
Cc: linux-media@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] AS3645A fixes
Date: Sat, 23 Sep 2017 21:39:31 +0200 [thread overview]
Message-ID: <a15c166f-48ec-faf8-a500-940fd912813a@gmail.com> (raw)
In-Reply-To: <076725cc-ef46-898d-34e5-099ece5d50b4@linux.intel.com>
Hi Sakari,
On 09/22/2017 11:25 PM, Sakari Ailus wrote:
> Hi Jacek,
>
> (Fixed DT list address.)
>
> Jacek Anaszewski wrote:
>> Hi Sakari,
>>
>> On 09/22/2017 11:32 AM, Sakari Ailus wrote:
>>> Hi Jacek and others,
>>>
>>> Here are a few fixes for the as3645a DTS as well as changes in bindings.
>>> The driver is not in a release yet.
>>>
>>> Jacek: Could you take these to your fixes branch so we don't get
>>> faulty DT
>>> bindings to a release? I've dropped the patches related to LED naming
>>> and
>>> label property as the discusion appears to continue on that.
>>
>> No problem. One question - isn't patch 3/4 missing?
>
> Hmm. I can see it on both linux-leds and devicetree.
>
> I've pushed the four patches here, on v4.14-rc1:
>
> <URL:https://git.linuxtv.org/sailus/media_tree.git/log/?h=as3645a-fix>
I turned out that gmail treated your patches as spam due
to your "resend" patch set.
Patch set applied to the fixes-4.14-rc3 branch of linux-leds.git.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2017-09-23 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 9:32 [PATCH v3 0/4] AS3645A fixes Sakari Ailus
2017-09-22 9:32 ` [PATCH v3 1/4] as3645a: Use ams,input-max-microamp as documented in DT bindings Sakari Ailus
2017-09-22 9:32 ` [PATCH v3 2/4] dt: bindings: as3645a: Use LED number to refer to LEDs Sakari Ailus
2017-09-22 9:32 ` [PATCH v3 3/4] as3645a: Use integer numbers for parsing LEDs Sakari Ailus
2017-09-22 9:32 ` [PATCH v3 4/4] as3645a: Unregister indicator LED on device unbind Sakari Ailus
2017-09-22 19:37 ` [PATCH v3 0/4] AS3645A fixes Jacek Anaszewski
[not found] ` <650b7cb3-f7dd-5959-3147-df7284415521-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-22 21:25 ` Sakari Ailus
2017-09-23 19:39 ` Jacek Anaszewski [this message]
[not found] ` <a15c166f-48ec-faf8-a500-940fd912813a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-24 13:56 ` Sakari Ailus
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=a15c166f-48ec-faf8-a500-940fd912813a@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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).