From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [PATCH] ASoC: Intel: atom: Make some messages to debug level
Date: Mon, 28 Nov 2016 21:23:32 +0530 [thread overview]
Message-ID: <20161128155331.GH6408@localhost> (raw)
In-Reply-To: <20161128152640.29566-1-tiwai@suse.de>
On Mon, Nov 28, 2016 at 04:26:40PM +0100, Takashi Iwai wrote:
> Intel sst driver spews lots of kernel messages in INFO level;
> typically, it gives a kernel message at each time it allocates or
> frees a stream, or at each time when a stream is started or stopped.
> This will piles up quickly, and it's almost useless for normal users,
> so let's hide them to KERN_DEBUG level.
Acked-by: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
next prev parent reply other threads:[~2016-11-28 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 15:26 [PATCH] ASoC: Intel: atom: Make some messages to debug level Takashi Iwai
2016-11-28 15:53 ` Vinod Koul [this message]
2016-11-29 11:45 ` Applied "ASoC: Intel: atom: Make some messages to debug level" to the asoc tree Mark Brown
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=20161128155331.GH6408@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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.