From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: tlv320dac33: Fix inconsistent spinlock usage
Date: Fri, 18 Mar 2011 13:20:24 +0000 [thread overview]
Message-ID: <20110318132023.GB677@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1300454111-27452-1-git-send-email-peter.ujfalusi@nokia.com>
On Fri, Mar 18, 2011 at 03:15:11PM +0200, Peter Ujfalusi wrote:
> The lock is used within the interrupt handler.
> Correct the spinlock usage, and use irqsave/irqrestore
> flavour of spin_lock/unlock.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@nokia.com>
Acked-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
next prev parent reply other threads:[~2011-03-18 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 13:15 [PATCH] ASoC: tlv320dac33: Fix inconsistent spinlock usage Peter Ujfalusi
2011-03-18 13:20 ` Mark Brown [this message]
2011-03-22 18:10 ` Liam Girdwood
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=20110318132023.GB677@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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;
as well as URLs for NNTP newsgroup(s).