From: Mark Brown <broonie@kernel.org>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Imre Deak <imre.deak@intel.com>
Subject: Re: [PATCH] ASoC: Intel: byt/hsw: Add missing kthread_stop to error/cleanup path
Date: Sun, 1 Jun 2014 11:45:05 +0100 [thread overview]
Message-ID: <20140601104505.GX5099@sirena.org.uk> (raw)
In-Reply-To: <1401436349-19202-1-git-send-email-jarkko.nikula@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 276 bytes --]
On Fri, May 30, 2014 at 10:52:29AM +0300, Jarkko Nikula wrote:
> From: Imre Deak <imre.deak@intel.com>
>
> Baytrail and Haswell SST IPC don't stop the kernel thread in error and
> cleanup path thus leaving orphan kernel thread behind in such a case.
Applied, thanks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2014-06-01 10:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 7:52 [PATCH] ASoC: Intel: byt/hsw: Add missing kthread_stop to error/cleanup path Jarkko Nikula
2014-06-01 10:45 ` Mark Brown [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=20140601104505.GX5099@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=imre.deak@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.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