From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dan Williams <djbw@fb.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Vinod Koul <vinod.koul@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] dmaengine: make dmatest less noisy
Date: Mon, 19 Aug 2013 11:51:06 +0300 [thread overview]
Message-ID: <1376902266.403.152.camel@smile> (raw)
In-Reply-To: <CAA9_cmfKhdQMk7uaczOH9o8kXJQ1WNtkNSvL61pWVRrBaC6gCQ@mail.gmail.com>
On Mon, 2013-08-19 at 01:49 -0700, Dan Williams wrote:
> On Mon, Aug 19, 2013 at 1:37 AM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > 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.
> >>
> >> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> >> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> >
> >> --- a/drivers/dma/dmatest.c
> >> +++ b/drivers/dma/dmatest.c
> >
> >> @@ -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));
> >
> > This is the idea behind original DMATEST module logic.
> > As far as I understand we would like to have them as warnings in case
> > when driver is compiled in and tests are run from the beginning.
> >
> > Though, I sent a correction patch that moves "No error" messages to
> > debug level which, I think, makes sense. I don't know why Dan still keep
> > silent on my last message in the discussion [1].
> >
>
> Applying them now, and yes I agree with your patch to take this back
> to the original implementation of not squawking on success.
Thank you!
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2013-08-19 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 8:25 [PATCH v2] dmaengine: make dmatest less noisy Linus Walleij
2013-08-19 8:31 ` Joe Perches
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 [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=1376902266.403.152.camel@smile \
--to=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