From: Vinod Koul <vinod.koul@intel.com>
To: Pan Bian <bianpan2016@163.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dmaengine: ioat: set error code on failures
Date: Tue, 6 Dec 2016 10:29:54 +0530 [thread overview]
Message-ID: <20161206045954.GO6408@localhost> (raw)
In-Reply-To: <1480690141-2858-1-git-send-email-bianpan2016@163.com>
On Fri, Dec 02, 2016 at 10:49:01PM +0800, Pan Bian wrote:
> In function ioat_dma_self_test(), when the calls to dma_mapping_error()
> fails, the value of return variable err is 0 (indicates no error). As a
> result, the return value may be inconsistent with the execution status.
> This patch fixes the bug by assigning -ENOMEM to err on the error path.
This was v2 of the series so you should tag it as PATCH v2. You can do so
with --subject-prefix in git format-patch command.
Applied both now with Dave's Acks
--
~Vinod
prev parent reply other threads:[~2016-12-06 4:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 14:49 [PATCH 1/2] dmaengine: ioat: set error code on failures Pan Bian
2016-12-06 4:59 ` Vinod Koul [this message]
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=20161206045954.GO6408@localhost \
--to=vinod.koul@intel.com \
--cc=Julia.Lawall@lip6.fr \
--cc=bianpan2016@163.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox