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
Subject: [2/2] dmaengine: dmatest: add norandom option
Date: Wed, 31 Jan 2018 13:04:24 +0530 [thread overview]
Message-ID: <20180131073424.GW18649@localhost> (raw)
On Mon, Jan 22, 2018 at 06:44:41PM +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 in one run. This patch adds option norandom to disable random
> offset setup. Option noverify has been changed to disable data
> verification only.
This doesn't apply for me due to dependency on previous patch. Please rebase
and resend.
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
Subject: Re: [PATCH 2/2] dmaengine: dmatest: add norandom option
Date: Wed, 31 Jan 2018 13:04:24 +0530 [thread overview]
Message-ID: <20180131073424.GW18649@localhost> (raw)
In-Reply-To: <1516617881-30044-2-git-send-email-shunyong.yang@hxt-semitech.com>
On Mon, Jan 22, 2018 at 06:44:41PM +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 in one run. This patch adds option norandom to disable random
> offset setup. Option noverify has been changed to disable data
> verification only.
This doesn't apply for me due to dependency on previous patch. Please rebase
and resend.
--
~Vinod
next reply other threads:[~2018-01-31 7:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 7:34 Vinod Koul [this message]
2018-01-31 7:34 ` [PATCH 2/2] dmaengine: dmatest: add norandom option Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-02-01 3:57 [1/2] dmaengine: dmatest: change symbolic permissions to octal values Joe Perches
2018-02-01 3:57 ` [PATCH 1/2] " Joe Perches
2018-02-01 3:46 [1/2] " Viresh Kumar
2018-02-01 3:46 ` [PATCH 1/2] " Viresh Kumar
2018-02-01 3:45 [1/2] " Vinod Koul
2018-02-01 3:45 ` [PATCH 1/2] " Vinod Koul
2018-01-31 10:01 [1/2] " Viresh Kumar
2018-01-31 10:01 ` [PATCH 1/2] " Viresh Kumar
2018-01-31 7:38 [2/2] dmaengine: dmatest: add norandom option Yang Shunyong
2018-01-31 7:38 ` Re: [PATCH 2/2] " Yang, Shunyong
2018-01-30 10:04 [1/2] dmaengine: dmatest: change symbolic permissions to octal values Vinod Koul
2018-01-30 10:04 ` Re: [PATCH 1/2] " Vinod Koul
2018-01-29 6:26 [1/2] " Yang Shunyong
2018-01-29 6:26 ` Re: [PATCH 1/2] " Yang, Shunyong
2018-01-29 4:48 [1/2] " Vinod Koul
2018-01-29 4:48 ` [PATCH 1/2] " Vinod Koul
2018-01-22 10:44 [2/2] dmaengine: dmatest: add norandom option Yang Shunyong
2018-01-22 10:44 ` [PATCH 2/2] " Yang Shunyong
2018-01-22 10:44 [1/2] dmaengine: dmatest: change symbolic permissions to octal values Yang Shunyong
2018-01-22 10:44 ` [PATCH 1/2] " 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=20180131073424.GW18649@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 \
/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.