From: Joe Perches <joe@perches.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] ALSA: echoaudio: cleanup of unnecessary messages
Date: Tue, 04 Nov 2014 10:28:01 -0800 [thread overview]
Message-ID: <1415125681.23168.1.camel@perches.com> (raw)
In-Reply-To: <1415125074-28006-1-git-send-email-sudipm.mukherjee@gmail.com>
On Tue, 2014-11-04 at 23:47 +0530, Sudip Mukherjee wrote:
> commit "b5b4a41b392960010fccf1f9ccf8334d612bd450" was dereferencing
> chip after it has been freed. This patch fixes that and at the same
> time removes some debugging messages, which are unnecessary, as they
> are just printing information about entry and exit from a function.
> This information we can easily get from ftrace.
Mostly true.
> diff --git a/sound/pci/echoaudio/echoaudio.c b/sound/pci/echoaudio/echoaudio.c
[]
> @@ -763,10 +755,8 @@ static int pcm_trigger(struct snd_pcm_substream *substream, int cmd)
> spin_lock(&chip->lock);
> switch (cmd) {
> case SNDRV_PCM_TRIGGER_RESUME:
> - dev_dbg(chip->card->dev, "pcm_trigger resume\n");
> case SNDRV_PCM_TRIGGER_START:
> case SNDRV_PCM_TRIGGER_PAUSE_RELEASE:
> - dev_dbg(chip->card->dev, "pcm_trigger start\n");
> for (i = 0; i < DSP_MAXPIPES; i++) {
> if (channelmask & (1 << i)) {
> pipe = chip->substream[i]->runtime->private_data;
These may not be useful but this switch state information
can't be got from ftrace.
next prev parent reply other threads:[~2014-11-04 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 18:17 [PATCH] ALSA: echoaudio: cleanup of unnecessary messages Sudip Mukherjee
2014-11-04 18:28 ` Joe Perches [this message]
2014-11-05 7:01 ` Sudip Mukherjee
2014-11-05 7:09 ` Takashi Iwai
2014-11-05 8:48 ` Sudip Mukherjee
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=1415125681.23168.1.camel@perches.com \
--to=joe@perches.com \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sudipm.mukherjee@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox