mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Wallis <awallis@codeaurora.org>
To: "Yang, Shunyong" <shunyong.yang@hxt-semitech.com>,
	"vinod.koul@intel.com" <vinod.koul@intel.com>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Zheng, Joey" <yu.zheng@hxt-semitech.com>,
	"okaya@codeaurora.org" <okaya@codeaurora.org>,
	"graham.moore@linux.intel.com" <graham.moore@linux.intel.com>
Subject: Re: [PATCH] dmaengine: dmatest: fix container_of member in dmatest_callback
Date: Wed, 24 Jan 2018 13:34:39 -0500	[thread overview]
Message-ID: <ba859f5a-905f-a980-847d-66b7454f01db@codeaurora.org> (raw)
In-Reply-To: <1516758463.2764.2.camel@hxt-semitech.com>

Vinod,

On 1/23/2018 8:47 PM, Yang, Shunyong wrote:
> Hi, Adam
> 
> On Tue, 2018-01-23 at 09:32 -0500, Adam Wallis wrote:
>> On 1/22/2018 2:28 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>
[..]
>>>
>> Thanks for the catch
>>
>> Acked-by: Adam Wallis <awallis@codeaurora.org>
> 
> Thanks!
> 
> Shunyong
> 

Can we get this fix into the 4.16 kernel? This is an important fix.

Thanks

Adam

-- 
Adam Wallis
Qualcomm Datacenter Technologies as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

  reply	other threads:[~2018-01-24 18:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22  7:28 Yang Shunyong
2018-01-23 14:32 ` Adam Wallis
2018-01-24  1:47   ` Yang, Shunyong
2018-01-24 18:34     ` Adam Wallis [this message]
2018-02-11  9:28   ` Wen He
2018-02-13  5:54     ` Yang, Shunyong
2018-01-29  4:45 ` Vinod Koul
2018-01-29  6:21   ` 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=ba859f5a-905f-a980-847d-66b7454f01db@codeaurora.org \
    --to=awallis@codeaurora.org \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=graham.moore@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okaya@codeaurora.org \
    --cc=shunyong.yang@hxt-semitech.com \
    --cc=vinod.koul@intel.com \
    --cc=yu.zheng@hxt-semitech.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
Powered by JetHome