linux-kernel - Re: [PATCH v4 0/3] gpio-charger: add devicetree support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 26 Oct 2014 13:06:28 +0100
From:	Heiko Stübner <heiko@...ech.de>
To:	sre@...nel.org
Cc:	dbaryshkov@...il.com, dwmw2@...radead.org,
	linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org, robh+dt@...nel.org,
	mark.rutland@....com, pawel.moll@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	dianders@...omium.org
Subject: Re: [PATCH v4 0/3] gpio-charger: add devicetree support

Hi Sebastian,

Am Dienstag, 23. September 2014, 22:42:13 schrieb Heiko Stuebner:
> This series adds devicetree support to the gpio-charger and fixes a small
> issue with the return value of gpio_get_value.
> 
> changes since v3:
> - remove of_match_ptr. All used of_xx function have stubs for !OF
>   and of_device_id also is always defined, so no need for of_match_ptr
> changes since v2:
> - fix (hopefully all) issues pointed out by Doug Anderson
> - add missing of_node assignment to charger
> changes since v1:
> - adapt binding example to show how the charger fits into the
>   power-supplies structure
> 
> 
> Heiko Stuebner (3):
>   dt-bindings: document gpio-charger bindings
>   power: gpio-charger: add device tree support
>   power: gpio-charger: do not use gpio value directly

I can see patch3 in your tree (and 3.18-rc). Will you take patches 1 and 2 for 
3.19?

The generally used 3 week period for devicetree-binding related complaints 
also should be over by now.


Heiko
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/