From: Vinod Koul <vinod.koul@intel.com>
To: Yang Shunyong <shunyong.yang@hxt-semitech.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, yu.zheng@hxt-semitch.com
Subject: [v2] dmaengine: dmatest: fix container_of member in dmatest_callback
Date: Tue, 30 Jan 2018 12:25:23 +0530 [thread overview]
Message-ID: <20180130065522.GO18649@localhost> (raw)
On Mon, Jan 29, 2018 at 02:40:11PM +0800, Yang Shunyong wrote:
> The type of arg passed to dmatest_callback is struct dmatest_done.
> It refers to test_done in struct dmatest_thread, not done_wait.
Applied, thanks
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Yang Shunyong <shunyong.yang@hxt-semitech.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, yu.zheng@hxt-semitch.com
Subject: Re: [PATCH v2] dmaengine: dmatest: fix container_of member in dmatest_callback
Date: Tue, 30 Jan 2018 12:25:23 +0530 [thread overview]
Message-ID: <20180130065522.GO18649@localhost> (raw)
In-Reply-To: <1517208011-7640-1-git-send-email-shunyong.yang@hxt-semitech.com>
On Mon, Jan 29, 2018 at 02:40:11PM +0800, Yang Shunyong wrote:
> The type of arg passed to dmatest_callback is struct dmatest_done.
> It refers to test_done in struct dmatest_thread, not done_wait.
Applied, thanks
--
~Vinod
next reply other threads:[~2018-01-30 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 6:55 Vinod Koul [this message]
2018-01-30 6:55 ` [PATCH v2] dmaengine: dmatest: fix container_of member in dmatest_callback Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-01-29 13:17 [v2] " Adam Wallis
2018-01-29 13:17 ` [PATCH v2] " Adam Wallis
2018-01-29 6:40 [v2] " Yang Shunyong
2018-01-29 6:40 ` [PATCH v2] " Yang Shunyong
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=20180130065522.GO18649@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shunyong.yang@hxt-semitech.com \
--cc=yu.zheng@hxt-semitch.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.