linux-kernel - Re: [PATCH V2 1/3] pinctrl: add utility functions for add map/configs

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 05 Aug 2013 15:37:54 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Laxman Dewangan <ldewangan@...dia.com>
CC:	linus.walleij@...aro.org, ian.campbell@...rix.com,
	rob.herring@...xeda.com, pawel.moll@....com, mark.rutland@....com,
	rob@...dley.net, sameo@...ux.intel.com, lee.jones@...aro.org,
	grant.likely@...aro.org, broonie@...nel.org,
	devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, gg@...mlogic.co.uk, kishon@...com
Subject: Re: [PATCH V2 1/3] pinctrl: add utility functions for add map/configs

On 08/05/2013 01:33 AM, Laxman Dewangan wrote:
> Some of pincontrol driver needs the utility function to create map
> list. The utility function needed for adding mux, configs etc.
> 
> In place of duplicating this in each driver, add the common utility
> function in common file and use from device specific driver. This will
> reduce the duplicating of code across drivers.

This patch,
Reviewed-by: Stephen Warren <swarren@...dia.com>

Some more documentation mnight be useful though, now these are common
utility functions rather than just some internal functions in the Tegra
pinctrl driver.

Hopefully there will be a patch to convert at least the Tegra pinctrl
driver to use these new functions.
--
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/