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]
Message-ID: <20120511131454.GI1214@sortiz-mobl>
Date:	Fri, 11 May 2012 15:14:54 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	Laxman Dewangan <ldewangan@...dia.com>
Cc:	grant.likely@...retlab.ca, linus.walleij@...ricsson.com,
	broonie@...nsource.wolfsonmicro.com, jedu@...mlogic.co.uk,
	lrg@...mlogic.co.uk, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] mfd:tps65910: use devm_* and register gpio as
 platform driver

Hi Laxman,

On Wed, May 09, 2012 at 06:40:53PM +0530, Laxman Dewangan wrote:
> This series does cleanup in the mfd/tps65910 as follows:
> - Do not cache the register when initailizing regmap. Cache when
>   actually when we need it.
> - Convert the allocation to use devm_* apis.
> - Move the gpio as platform driver and register it as mfd sub devices.
> 
> Laxman Dewangan (4):
>   mfd: tps65910: cache register when we need it
> 	Remove the chaching of register in regmap initialization.
> 
>   mfd: tps65910: convert all allocation to devm_*
> 	Convert the allocation to use devm_* apis.
> 
>   mfd: tps65910: register gpio as mfd device
>   gpio: tps65910: move this as platform driver
> 	Above two patch to make gpio driver as platform driver and register
> 	as mfd sub device from core driver.
> 	
I applied patches 1, 2 and 3. Patch #4 does not apply cleanly to my for-next
branch, could you please rebase it ?
Also, having Grant's ACK for it would be nice.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ