From: Adam Wallis <awallis@codeaurora.org>
To: Yang Shunyong <shunyong.yang@hxt-semitech.com>, vinod.koul@intel.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: Mon, 29 Jan 2018 08:17:26 -0500 [thread overview]
Message-ID: <6ca31eff-f566-aefe-1364-b488f49117ed@codeaurora.org> (raw)
Yang,
On 1/29/2018 1:40 AM, 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.
>
> Fixes: 6f6a23a213be ("dmaengine: dmatest: move callback wait ...")
> Signed-off-by: Yang Shunyong <shunyong.yang@hxt-semitech.com>
> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
> ---
>
> v2: change arg to done in container_of().
>
> ---
> drivers/dma/dmatest.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/dmatest.c b/drivers/dma/dmatest.c
> index ec5f9d2bc820..80cc2be6483c 100644
> --- a/drivers/dma/dmatest.c
> +++ b/drivers/dma/dmatest.c
> @@ -355,7 +355,7 @@ static void dmatest_callback(void *arg)
> {
> struct dmatest_done *done = arg;
> struct dmatest_thread *thread =
> - container_of(arg, struct dmatest_thread, done_wait);
> + container_of(done, struct dmatest_thread, test_done);
> if (!thread->done) {
> done->done = true;
> wake_up_all(done->wait);
>
Thanks again for the fix (and to Vinod for the cleanup)
Acked-by: Adam Wallis <awallis@codeaurora.org>
next reply other threads:[~2018-01-29 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 13:17 Adam Wallis [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-30 6:55 [v2] dmaengine: dmatest: fix container_of member in dmatest_callback Vinod Koul
2018-01-29 6:40 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=6ca31eff-f566-aefe-1364-b488f49117ed@codeaurora.org \
--to=awallis@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shunyong.yang@hxt-semitech.com \
--cc=vinod.koul@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).