All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Jacek Anaszewski
	<jacek.anaszewski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH v3 0/4] AS3645A fixes
Date: Sat, 23 Sep 2017 00:25:39 +0300	[thread overview]
Message-ID: <076725cc-ef46-898d-34e5-099ece5d50b4@linux.intel.com> (raw)
In-Reply-To: <650b7cb3-f7dd-5959-3147-df7284415521-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

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>

-- 
Sakari Ailus
sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.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 00:25:39 +0300	[thread overview]
Message-ID: <076725cc-ef46-898d-34e5-099ece5d50b4@linux.intel.com> (raw)
In-Reply-To: <650b7cb3-f7dd-5959-3147-df7284415521@gmail.com>

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>

-- 
Sakari Ailus
sakari.ailus@linux.intel.com

  parent reply	other threads:[~2017-09-22 21:25 UTC|newest]

Thread overview: 11+ 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 [this message]
2017-09-22 21:25       ` Sakari Ailus
2017-09-23 19:39       ` Jacek Anaszewski
     [not found]         ` <a15c166f-48ec-faf8-a500-940fd912813a-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-24 13:56           ` Sakari Ailus
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=076725cc-ef46-898d-34e5-099ece5d50b4@linux.intel.com \
    --to=sakari.ailus-vuqaysv1563yd54fqh9/ca@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jacek.anaszewski-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-leds-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-media-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.