linux-kernel - Re: [PATCH 1/3] dw_mmc: Don't loop when handling an interrupt

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: <87a9q7fk9l.fsf@octavius.laptop.org>
Date:	Wed, 13 Mar 2013 10:26:46 -0400
From:	Chris Ball <cjb@...top.org>
To:	Seungwon Jeon <tgih.jun@...sung.com>
Cc:	'Markos Chandras' <markos.chandras@...tec.com>,
	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
	'Jaehoon Chung' <jh80.chung@...sung.com>
Subject: Re: [PATCH 1/3] dw_mmc: Don't loop when handling an interrupt

Hi,

On Wed, Mar 13 2013, Seungwon Jeon wrote:
> On Tuesday, March 12, 2013, Markos Chandras wrote:
>> There is no reason to loop when handling an interrupt. The "if" clauses
>> will handle all of them sequentially. This also eliminates the extra loop
>> we used to take with no pending interrupts and we ended up breaking out
>> of the while loop.
>> 
>> Signed-off-by: Markos Chandras <markos.chandras@...tec.com>
>> Cc: Seungwon Jeon <tgih.jun@...sung.com>
>
> Acked-by: Seungwon Jeon <tgih.jun@...sung.com>
>
> You can add my ack to other patches.
> However, could you change the subject prefix to 'mmc: dw_mmc' and resend?

It's okay, I'll take care of that when applying this time.  Thanks!

- Chris.
-- 
Chris Ball   <cjb@...top.org>   <http://printf.net/>
One Laptop Per Child
--
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/