From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
patches@opensource.wolfsonmicro.com, lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: wm_adsp: Check return value from wm_adsp_buffer_init
Date: Tue, 22 Nov 2016 15:28:34 +0000 [thread overview]
Message-ID: <20161122152834.GA1867@localhost.localdomain> (raw)
In-Reply-To: <3aa7c6c7-07f8-2463-48d9-a0d5d73f2f82@sakamocchi.jp>
On Tue, Nov 22, 2016 at 05:22:17PM +0200, Takashi Sakamoto wrote:
> Charles,
>
> On Nov 22 2016 16:46, Charles Keepax wrote:
> > We are not checking the return value from a call to wm_adsp_buffer_init
> > it looks like this used to be returned at the bottom of the function but
> > probably got missed when more error paths were added. This patch adds
> > the appropriate error check.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> > ---
> > sound/soc/codecs/wm_adsp.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/sound/soc/codecs/wm_adsp.c b/sound/soc/codecs/wm_adsp.c
> > index 6ccb731..7e4f8dd 100644
> > --- a/sound/soc/codecs/wm_adsp.c
> > +++ b/sound/soc/codecs/wm_adsp.c
> > @@ -2580,8 +2580,11 @@ int wm_adsp2_event(struct snd_soc_dapm_widget *w,
> >
> > mutex_lock(&dsp->pwr_lock);
> >
> > - if (wm_adsp_fw[dsp->fw].num_caps != 0)
> > + if (wm_adsp_fw[dsp->fw].num_caps != 0) {
> > ret = wm_adsp_buffer_init(dsp);
> > + if (ret < 0)
> > + goto err;
> > + }
>
> Need to call mutex_unlock() before jumping to err label?
>
Thanks, will respin.
Thanks,
Charles
prev parent reply other threads:[~2016-11-22 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 14:46 [PATCH] ASoC: wm_adsp: Check return value from wm_adsp_buffer_init Charles Keepax
2016-11-22 15:22 ` Takashi Sakamoto
2016-11-22 15:28 ` Charles Keepax [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=20161122152834.GA1867@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=o-takashi@sakamocchi.jp \
--cc=patches@opensource.wolfsonmicro.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.