From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
YuanZhe Liu <25031212351@stu.xidian.edu.cn>
Subject: Re: [PATCH 5.15.y v2] ALSA: hwdep: Serialize DSP load requests
Date: Thu, 12 Nov 2026 21:33:15 -0500 [thread overview]
Message-ID: <daily-reply-2026-11-12-5937566686@kernel.org> (raw)
In-Reply-To: <20261112013952.8019-1-25031212351@stu.xidian.edu.cn>
On 2026-11-12, YuanZhe Liu wrote:
> [PATCH 5.15.y v2] ALSA: hwdep: Serialize DSP load requests
> The check of the loaded DSP indices and the call of the driver's
> dsp_load callback in snd_hwdep_dsp_load() are not serialized. A hwdep
> file descriptor can be shared among threads, or inherited across fork,
Queued for 5.15 and 5.10, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-13 2:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 1:25 FAILED: patch "[PATCH] ALSA: hwdep: Serialize DSP load requests" failed to apply to 5.10-stable tree Sasha Levin
2026-11-11 4:18 ` [PATCH 5.10.y] ALSA: hwdep: Serialize DSP load requests YuanZhe Liu
2026-11-11 21:54 ` Sasha Levin
2026-11-12 1:39 ` [PATCH 5.10.y v2] " YuanZhe Liu
2026-11-12 1:39 ` [PATCH 5.15.y " YuanZhe Liu
2026-11-13 2:33 ` Sasha Levin [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=daily-reply-2026-11-12-5937566686@kernel.org \
--to=sashal@kernel.org \
--cc=25031212351@stu.xidian.edu.cn \
--cc=stable@vger.kernel.org \
/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