linux-kernel - Re: [PATCH 2/3] mfd: MAX8998: Add interrupts 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 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:	Tue, 20 Jul 2010 18:54:04 +0900
From:	Joonyoung Shim <jy0922.shim@...sung.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, sameo@...ux.intel.com,
	lrg@...mlogic.co.uk, akpm@...ux-foundation.org,
	a.zummo@...ertech.it, gortmaker@...oo.com,
	kyungmin.park@...sung.com, m.szyprowski@...sung.com
Subject: Re: [PATCH 2/3] mfd: MAX8998: Add interrupts support

On 7/20/2010 5:55 PM, Mark Brown wrote:
> On Tue, Jul 20, 2010 at 03:57:37PM +0900, Joonyoung Shim wrote:
>> Use genirq and provide seperated file for interrupts support.
>>
>> Signed-off-by: Joonyoung Shim <jy0922.shim@...sung.com>
>> Signed-off-by: Kyungmin Park <kyungmin.park@...sung.com>
> 
> ...
> 
>> +
>> +	for (i = 0; i < ARRAY_SIZE(max8998->irq_masks_cur); i++) {
>> +		/*
>> +		 * If there's been a change in the mask write it back
>> +		 * to the hardware.
>> +		 */
>> +		if (max8998->irq_masks_cur[i] != max8998->irq_masks_cache[i]) {
>> +			max8998->irq_masks_cache[i] = max8998->irq_masks_cur[i];
>> +			max8998_write_reg(max8998->i2c, MAX8998_REG_IRQM1 + i,
>> +					max8998->irq_masks_cur[i]);
>> +		}
> 
> This code all looks oddly familiar :)

Yes, i didn't have any needs to use other way.

> 
> Reviewed-by: Mark Brown <broonie@...nsource.wolfsonmicro.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/