From: Chanwoo Choi <cw00.choi@samsung.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, sameo@linux.intel.com,
broonie@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org, kyungmin.park@samsung.com,
myungjoo.ham@samsung.com
Subject: Re: [PATCH v2 0/2] input: add MAX8997-haptic driver
Date: Tue, 13 Mar 2012 14:39:04 +0900 [thread overview]
Message-ID: <4F5EDD78.4070701@samsung.com> (raw)
In-Reply-To: <20120313053035.GB9449@core.coreip.homeip.net>
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
prev parent reply other threads:[~2012-03-13 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 8:02 [PATCH v2 0/2] input: add MAX8997-haptic driver Chanwoo Choi
2012-03-07 8:29 ` Dmitry Torokhov
2012-03-12 8:31 ` Chanwoo Choi
2012-03-13 5:30 ` Dmitry Torokhov
2012-03-13 5:39 ` Chanwoo Choi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F5EDD78.4070701@samsung.com \
--to=cw00.choi@samsung.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=sameo@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.