From: Takashi Iwai <tiwai@suse.de>
To: Wu Bo <wubo40@huawei.com>
Cc: <perex@perex.cz>, <tiwai@suse.com>, <libin.yang@linux.intel.com>,
<kai.vehmanen@linux.intel.com>, <nmahale@nvidia.com>,
<aplattner@nvidia.com>, <pierre-louis.bossart@linux.intel.com>,
<linux-kernel@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<liuzhiqiang26@huawei.com>, <linfeilong@huawei.com>
Subject: Re: [PATCH] sound:hdmi:fix without unlocked before return
Date: Wed, 29 Apr 2020 09:27:53 +0200 [thread overview]
Message-ID: <s5hees6lpja.wl-tiwai@suse.de> (raw)
In-Reply-To: <1587907042-694161-1-git-send-email-wubo40@huawei.com>
On Sun, 26 Apr 2020 15:17:22 +0200,
Wu Bo wrote:
>
> Fix the following coccicheck warning:
> sound/pci/hda/patch_hdmi.c:1852:2-8: preceding lock on line 1846
>
> After add sanity check to pass klockwork check,
> The spdif_mutex should be unlock before return true
> in check_non_pcm_per_cvt().
>
> Signed-off-by: Wu Bo <wubo40@huawei.com>
Applied now with the correction of subject and Fixes tag as well as
Cc-to-stable tag.
thanks,
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Wu Bo <wubo40@huawei.com>
Cc: pierre-louis.bossart@linux.intel.com, nmahale@nvidia.com,
kai.vehmanen@linux.intel.com, aplattner@nvidia.com,
linux-kernel@vger.kernel.org, tiwai@suse.com,
linfeilong@huawei.com, libin.yang@linux.intel.com,
alsa-devel@alsa-project.org, liuzhiqiang26@huawei.com
Subject: Re: [PATCH] sound:hdmi:fix without unlocked before return
Date: Wed, 29 Apr 2020 09:27:53 +0200 [thread overview]
Message-ID: <s5hees6lpja.wl-tiwai@suse.de> (raw)
In-Reply-To: <1587907042-694161-1-git-send-email-wubo40@huawei.com>
On Sun, 26 Apr 2020 15:17:22 +0200,
Wu Bo wrote:
>
> Fix the following coccicheck warning:
> sound/pci/hda/patch_hdmi.c:1852:2-8: preceding lock on line 1846
>
> After add sanity check to pass klockwork check,
> The spdif_mutex should be unlock before return true
> in check_non_pcm_per_cvt().
>
> Signed-off-by: Wu Bo <wubo40@huawei.com>
Applied now with the correction of subject and Fixes tag as well as
Cc-to-stable tag.
thanks,
Takashi
next prev parent reply other threads:[~2020-04-29 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 13:17 [PATCH] sound:hdmi:fix without unlocked before return Wu Bo
2020-04-26 13:17 ` Wu Bo
2020-04-29 7:27 ` Takashi Iwai [this message]
2020-04-29 7:27 ` Takashi Iwai
2020-04-30 4:37 ` Wu Bo
2020-04-30 4:37 ` Wu Bo
2020-04-26 17:00 Markus Elfring
2020-04-26 17:00 ` Markus Elfring
2020-04-26 17:00 ` Markus Elfring
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=s5hees6lpja.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=aplattner@nvidia.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=libin.yang@linux.intel.com \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuzhiqiang26@huawei.com \
--cc=nmahale@nvidia.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=wubo40@huawei.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.