From: Tomoya MORINAGA <tomoya-linux@dsn.okisemi.com>
To: Vinod Koul <vkoul@infradead.org>
Cc: Alexander Stein <alexander.stein@systec-electronic.com>,
"Wang, Yong Y" <yong.y.wang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org, "Wang, Qi" <qi.wang@intel.com>,
"toshiharu-linux@dsn.okisemi.com"
<toshiharu-linux@dsn.okisemi.com>
Subject: Re: [PATCH] pch_dma: Fix channel locking
Date: Fri, 08 Jul 2011 08:51:01 +0900 [thread overview]
Message-ID: <4E164665.4030002@dsn.okisemi.com> (raw)
In-Reply-To: <1310002731.20150.5.camel@psiaudioba-mobl1>
(2011/07/07 10:38), Vinod Koul wrote:
> On Wed, 2011-06-29 at 19:26 +0900, Tomoya MORINAGA wrote:
>> (2011/06/29 15:28), Alexander Stein wrote:
>>> Are you sure you applied the patch? There shouldn't be a _raw_spin_lock_bh
>>> here.
>>>
>>
>> You are right.
>> I tested again, as a result,
>> I could confirm that after using your patch,
>> kernel error message doesn't logged at all.
>> It seems my patching yesterday was failed or operation mistake.
>> Sorry for the in inconvenience.
>>
> Care to send tested your by, before I apply this patch?
>
We are now doing long duration test.
After the test finish, I will report to you.
--
tomoya
OKI SEMICONDUCTOR CO., LTD.
next prev parent reply other threads:[~2011-07-07 23:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 15:05 [PATCH] pch_dma: Fix channel locking Alexander Stein
2011-06-23 0:11 ` Tomoya MORINAGA
2011-06-23 7:42 ` Alexander Stein
2011-06-24 5:28 ` Tomoya MORINAGA
2011-06-27 14:22 ` Alexander Stein
2011-06-28 10:34 ` Tomoya MORINAGA
2011-06-28 11:14 ` Alexander Stein
2011-06-29 4:04 ` Tomoya MORINAGA
2011-06-29 4:25 ` Tomoya MORINAGA
2011-06-29 6:28 ` Alexander Stein
2011-06-29 10:26 ` Tomoya MORINAGA
2011-07-07 1:38 ` Vinod Koul
2011-07-07 23:51 ` Tomoya MORINAGA [this message]
2011-07-08 7:08 ` Tomoya MORINAGA
2011-07-13 22:12 ` Koul, Vinod
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=4E164665.4030002@dsn.okisemi.com \
--to=tomoya-linux@dsn.okisemi.com \
--cc=alexander.stein@systec-electronic.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qi.wang@intel.com \
--cc=toshiharu-linux@dsn.okisemi.com \
--cc=vkoul@infradead.org \
--cc=yong.y.wang@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.