All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: Misael Lopez <misael.lopez@ti.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Linux Kernel-3.5 crashed as dapm is not supported by codec
Date: Fri, 9 Nov 2012 16:14:16 +0530	[thread overview]
Message-ID: <509CDE80.6080903@st.com> (raw)
In-Reply-To: <509BF772.7010607@ti.com>

Hello Misael

On 11/8/2012 11:48 PM, Misael Lopez wrote:
> The backtrace doesn't seem to point directly to codec's shutdown but
> system's. There is a problem in the way the card's codec list is
> traversed to perform the shutdown, please see [1]. Take a look at that
> patch, it might help with this kernel crash.
>
> Regards,
> -Misa
>
> [1]
> http://mailman.alsa-project.org/pipermail/alsa-devel/2012-November/056846.html

Thanks for the support. The patch works fine.

In case it is not added in the tree, you can add

Tested-by: Rajeev Kumar <rajeev-dlh.kumar@st.com>

Best Regards
Rajeev

  reply	other threads:[~2012-11-09 10:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 11:16 Linux Kernel-3.5 crashed as dapm is not supported by codec Rajeev kumar
2012-09-20 11:49 ` Mark Brown
2012-09-21  3:57   ` Rajeev kumar
2012-09-21 11:14     ` Mark Brown
2012-11-06 10:40     ` Rajeev kumar
2012-11-06 11:43       ` Mark Brown
2012-11-07  5:32         ` Rajeev kumar
2012-11-07 14:56           ` Mark Brown
2012-11-08  4:28             ` Rajeev kumar
2012-11-08 18:18               ` Misael Lopez
2012-11-09 10:44                 ` Rajeev kumar [this message]
2012-11-08 14:38       ` Péter Ujfalusi
2012-11-09 11:17         ` Rajeev kumar

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=509CDE80.6080903@st.com \
    --to=rajeev-dlh.kumar@st.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=misael.lopez@ti.com \
    --cc=peter.ujfalusi@ti.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 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.