From: Vinod Koul <vkoul@kernel.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: dmaengine@vger.kernel.org, seraj.alijan@sondrel.com
Subject: Re: [PATCH] dmaengine: dmatest: Restore default for channel
Date: Wed, 13 May 2020 17:00:49 +0530 [thread overview]
Message-ID: <20200513113049.GE14092@vkoul-mobl> (raw)
In-Reply-To: <20200429071522.58148-1-vladimir.murzin@arm.com>
On 29-04-20, 08:15, Vladimir Murzin wrote:
> In case of dmatest is built-in and no channel was configured test
> doesn't run with:
>
> dmatest: Could not start test, no channels configured
>
> Even though description to "channel" parameter claims that default is
> any.
>
> Add default channel back as it used to be rather than reject test with
> no channel configuration.
>
> Fixes: d53513d5dc285d9a95a534fc41c5c08af6b60eac ("dmaengine: dmatest: Add support for multi channel testing)
>
no need for blank line here
> Reported-by: Dijil Mohan <Dijil.Mohan@arm.com>
> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
> ---
> drivers/dma/dmatest.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/dma/dmatest.c b/drivers/dma/dmatest.c
> index a2cadfa..5e1fff9 100644
> --- a/drivers/dma/dmatest.c
> +++ b/drivers/dma/dmatest.c
> @@ -1166,10 +1166,11 @@ static int dmatest_run_set(const char *val, const struct kernel_param *kp)
> mutex_unlock(&info->lock);
> return ret;
> } else if (dmatest_run) {
> - if (is_threaded_test_pending(info))
> - start_threaded_tests(info);
> - else
> - pr_info("Could not start test, no channels configured\n");
> + if (!is_threaded_test_pending(info)){
We need space before {
That is why we need to run checkpatch before sending patches.
I have fixed that up and applied this
--
~Vinod
prev parent reply other threads:[~2020-05-13 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 7:15 [PATCH] dmaengine: dmatest: Restore default for channel Vladimir Murzin
2020-05-13 11:30 ` 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=20200513113049.GE14092@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=seraj.alijan@sondrel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).