From: Vinod Koul <vkoul@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org,
Vladimir Murzin <vladimir.murzin@arm.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH v2 1/3] dmaengine: dmatest: Prevent to run on misconfigured channel
Date: Tue, 22 Sep 2020 20:20:06 +0530 [thread overview]
Message-ID: <20200922145006.GB2968@vkoul-mobl> (raw)
In-Reply-To: <20200922115847.30100-1-andriy.shevchenko@linux.intel.com>
On 22-09-20, 14:58, Andy Shevchenko wrote:
> From: Vladimir Murzin <vladimir.murzin@arm.com>
>
> Andy reported that commit 6b41030fdc79 ("dmaengine: dmatest:
> Restore default for channel") broke his scripts for the case
> where "busy" channel is used for configuration with expectation
> that run command would do nothing. Instead, behavior was
> (unintentionally) changed to treat such case as under-configuration
> and progress with defaults, i.e. run command would start a test
> with default setting for channel (which would use all channels).
>
> Restore original behavior with tracking status of channel setter
> so we can distinguish between misconfigured and under-configured
> cases in run command and act accordingly.
Applied all, thanks
--
~Vinod
prev parent reply other threads:[~2020-09-22 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 11:58 [PATCH v2 1/3] dmaengine: dmatest: Prevent to run on misconfigured channel Andy Shevchenko
2020-09-22 11:58 ` [PATCH v2 2/3] dmaengine: dmatest: Check list for emptiness before access its last entry Andy Shevchenko
2020-09-22 11:58 ` [PATCH v2 3/3] dmaengine: dmatest: Return boolean result directly in filter() Andy Shevchenko
2020-09-22 14:50 ` 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=20200922145006.GB2968@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=vladimir.murzin@arm.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.