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,
Joey Zheng <yu.zheng@hxt-semitech.com>
Subject: [v3] dmaengine: dmatest: add norandom option
Date: Mon, 5 Feb 2018 11:11:57 +0530 [thread overview]
Message-ID: <20180205054157.GS18649@localhost> (raw)
On Fri, Feb 02, 2018 at 05:51:09PM +0800, Yang Shunyong wrote:
> Existing option noverify disables both random src/dst address offset
> setup and data verification. Sometimes, we need to control random
> src/dst address setup and verification separately, such as disabling
> random to make sure that test covers addresses in all interleaving
> banks, but data verification is still performed.
>
> This patch adds option norandom to disable random offset setup. Option
> noverify has been changed to disable data verification only.
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,
Joey Zheng <yu.zheng@hxt-semitech.com>
Subject: Re: [PATCH v3] dmaengine: dmatest: add norandom option
Date: Mon, 5 Feb 2018 11:11:57 +0530 [thread overview]
Message-ID: <20180205054157.GS18649@localhost> (raw)
In-Reply-To: <1517565069-19769-1-git-send-email-shunyong.yang@hxt-semitech.com>
On Fri, Feb 02, 2018 at 05:51:09PM +0800, Yang Shunyong wrote:
> Existing option noverify disables both random src/dst address offset
> setup and data verification. Sometimes, we need to control random
> src/dst address setup and verification separately, such as disabling
> random to make sure that test covers addresses in all interleaving
> banks, but data verification is still performed.
>
> This patch adds option norandom to disable random offset setup. Option
> noverify has been changed to disable data verification only.
Applied, thanks
--
~Vinod
next reply other threads:[~2018-02-05 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 5:41 Vinod Koul [this message]
2018-02-05 5:41 ` [PATCH v3] dmaengine: dmatest: add norandom option Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-02-02 9:51 [v3] " Yang Shunyong
2018-02-02 9:51 ` [PATCH v3] " 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=20180205054157.GS18649@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-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 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.