From: Joe Perches <joe@perches.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Vinod Koul <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org, Dan Williams <djbw@fb.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v2] dmaengine: make dmatest less noisy
Date: Mon, 19 Aug 2013 01:31:43 -0700 [thread overview]
Message-ID: <1376901103.26146.1.camel@joe-AO722> (raw)
In-Reply-To: <1376900724-9636-1-git-send-email-linus.walleij@linaro.org>
On Mon, 2013-08-19 at 10:25 +0200, Linus Walleij wrote:
> Commit 95019c8c5 "dmatest: gather test results in the linked list"
> started to warning whenever we add results to a test thread.
> A warning for something completely normal? This is just cluttering
> my terminal. Move to debug prints.
[]
> diff --git a/drivers/dma/dmatest.c b/drivers/dma/dmatest.c
[]
> @@ -36,7 +36,7 @@ static char test_device[20];
> module_param_string(device, test_device, sizeof(test_device), S_IRUGO);
> MODULE_PARM_DESC(device, "Bus ID of the DMA Engine to test (default: any)");
>
> -static unsigned int threads_per_chan = 1;
> +static unsigned int threads_per_chan = 8;
> module_param(threads_per_chan, uint, S_IRUGO);
> MODULE_PARM_DESC(threads_per_chan,
> "Number of threads to start per channel (default: 1)");
This is unrelated and makes the MODULE_PARAM_DESC below
it have the incorrect default.
> @@ -406,7 +406,7 @@ static int thread_result_add(struct dmatest_info *info,
> list_add_tail(&tr->node, &r->results);
> mutex_unlock(&info->results_lock);
>
> - pr_warn("%s\n", thread_result_get(r->name, tr));
> + pr_debug("%s\n", thread_result_get(r->name, tr));
> return 0;
> }
>
This bit is sensible though.
next prev parent reply other threads:[~2013-08-19 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 8:25 Linus Walleij
2013-08-19 8:31 ` Joe Perches [this message]
2013-08-19 9:54 ` Linus Walleij
2013-08-19 8:37 ` Andy Shevchenko
2013-08-19 8:49 ` Dan Williams
2013-08-19 8:51 ` Andy Shevchenko
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=1376901103.26146.1.camel@joe-AO722 \
--to=joe@perches.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=djbw@fb.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®