linux-kernel - Re: [PATCH V2] pinctrl: implement devm_pinctrl

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4F8906BD.1010601@codeaurora.org>
Date:	Fri, 13 Apr 2012 22:10:21 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Stephen Warren <swarren@...dotorg.org>
CC:	Linus Walleij <linus.walleij@...aro.org>,
	linux-kernel@...r.kernel.org, Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH V2] pinctrl: implement devm_pinctrl_get()/put()

On 4/13/2012 9:48 AM, Stephen Warren wrote:
> From: Stephen Warren <swarren@...dia.com>
>
> These functions allow the driver core to automatically clean up any
> allocations made by drivers, thus leading to simplified drivers.
>
> Signed-off-by: Stephen Warren <swarren@...dia.com>
> ---
> v2:
> * Updated documentation to describe and recommend using devm_* functions.
> * Added devm_pinctrl_get_select() and devm_pinctrl_get_select_default() to
>   consumer.h

Please also document it in Documentation/driver-model/devres.txt

> ---
>  Documentation/pinctrl.txt        |   48 +++++++++++++++++++-------------
>  drivers/pinctrl/core.c           |   56 ++++++++++++++++++++++++++++++++++++++
>  include/linux/pinctrl/consumer.h |   44 +++++++++++++++++++++++++++++
>  3 files changed, 129 insertions(+), 19 deletions(-)
>
-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

--
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/