From: Vinod Koul <vinod.koul@intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: dan.j.williams@intel.com, dave.jiang@intel.com,
bianpan2016@163.com, arvind.yadav.cs@gmail.com,
kjlx@templeofstupid.com, geliangtang@gmail.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] dmaengine: ioat: Fix error handling path
Date: Wed, 29 Nov 2017 14:28:35 +0000 [thread overview]
Message-ID: <20171129141634.GI32417@localhost> (raw)
In-Reply-To: <20171117213753.21050-1-christophe.jaillet@wanadoo.fr>
On Fri, Nov 17, 2017 at 10:37:53PM +0100, Christophe JAILLET wrote:
> If the last test in 'ioat_dma_self_test()' fails, we must release all
> the allocated resources and not just part of them.
Applied, thanks
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: dan.j.williams@intel.com, dave.jiang@intel.com,
bianpan2016@163.com, arvind.yadav.cs@gmail.com,
kjlx@templeofstupid.com, geliangtang@gmail.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] dmaengine: ioat: Fix error handling path
Date: Wed, 29 Nov 2017 19:46:35 +0530 [thread overview]
Message-ID: <20171129141634.GI32417@localhost> (raw)
In-Reply-To: <20171117213753.21050-1-christophe.jaillet@wanadoo.fr>
On Fri, Nov 17, 2017 at 10:37:53PM +0100, Christophe JAILLET wrote:
> If the last test in 'ioat_dma_self_test()' fails, we must release all
> the allocated resources and not just part of them.
Applied, thanks
--
~Vinod
next prev parent reply other threads:[~2017-11-29 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 21:37 [PATCH] dmaengine: ioat: Fix error handling path Christophe JAILLET
2017-11-17 21:37 ` Christophe JAILLET
2017-11-17 21:44 ` Dave Jiang
2017-11-17 21:44 ` Dave Jiang
2017-11-29 14:16 ` Vinod Koul [this message]
2017-11-29 14:28 ` Vinod Koul
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=20171129141634.GI32417@localhost \
--to=vinod.koul@intel.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=bianpan2016@163.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=geliangtang@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kjlx@templeofstupid.com \
--cc=linux-kernel@vger.kernel.org \
/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.