| 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
| ||
|
Date: Tue, 13 Mar 2012 14:39:04 +0900 From: Chanwoo Choi <cw00.choi@...sung.com> To: Dmitry Torokhov <dmitry.torokhov@...il.com> Cc: linux-input@...r.kernel.org, sameo@...ux.intel.com, broonie@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org, kyungmin.park@...sung.com, myungjoo.ham@...sung.com Subject: Re: [PATCH v2 0/2] input: add MAX8997-haptic driver On 03/13/2012 02:30 PM, Dmitry Torokhov wrote: > On Mon, Mar 12, 2012 at 05:31:24PM +0900, Chanwoo Choi wrote: >> Hi Dmitry, >> >> On 03/07/2012 05:29 PM, Dmitry Torokhov wrote: >>> Hi Chanwoo, >>> >>> >>> On Wed, Mar 07, 2012 at 05:02:49PM +0900, Chanwoo Choi wrote: >>>> MAX8997 has several features in a single chip, >>>> This patchset supports unimplemented haptic driver of MAX8997. >>>> >>>> v2 >>>> - code clean and remove unnecessary code according to comment of Dmitry >>>> Torokhov >>> >>> Could you please tell me if the version of the patch I sent to you >>> worked or not? >> >> It isn't worked because it use the mutex lock in irq handler stack. >> so, I resend v3 patch of max8997-haptic driver after modifying it. > > Hmm, my patch did not add taking mutex in irq context, I presume you are > talking about max8997->iolock that is taken in max8997_write_reg... OK, > I see... > You're right. I'm sorry about my ambiguous reply for you. Best Regards, Chanwoo Choi -- 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