From: Liam Girdwood <liam.r.girdwood@intel.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [alsa-devel] [patch 1/2] ASoC: sst-haswell-ipc: restore IRQs on error
Date: Tue, 25 Feb 2014 13:12:11 +0000 [thread overview]
Message-ID: <1393333931.2300.11.camel@loki> (raw)
In-Reply-To: <20140225083250.GA22416@elgon.mountain>
On Tue, 2014-02-25 at 11:32 +0300, Dan Carpenter wrote:
> This should be spin_unlock_irqrestore() instead of spin_unlock()
>
> Fixes: 22981243589c ('ASoC: Intel: Add Haswell/Broadwell IPC')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/sound/soc/intel/sst-haswell-ipc.c b/sound/soc/intel/sst-haswell-ipc.c
> index 668d486520ae..552aebf2c8f5 100644
> --- a/sound/soc/intel/sst-haswell-ipc.c
> +++ b/sound/soc/intel/sst-haswell-ipc.c
> @@ -527,7 +527,7 @@ static int ipc_tx_message(struct sst_hsw *hsw, u32 header, void *tx_data,
>
> msg = msg_get_empty(hsw);
> if (msg == NULL) {
> - spin_unlock(&hsw->dsp->spinlock);
> + spin_unlock_irqrestore(&hsw->dsp->spinlock, flags);
> return -EBUSY;
> }
>
Both
Acked-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2014-02-25 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 8:32 [patch 1/2] ASoC: sst-haswell-ipc: restore IRQs on error Dan Carpenter
2014-02-25 13:12 ` Liam Girdwood [this message]
2014-02-25 23:46 ` 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=1393333931.2300.11.camel@loki \
--to=liam.r.girdwood@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lgirdwood@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