From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Takashi Iwai <tiwai@suse.de>, <linux-sound@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] ALSA/ASoC: hda: Fix race between unsol events and unbind
Date: Fri, 9 Oct 2026 09:44:48 +0200 [thread overview]
Message-ID: <eba0472e-5bf0-471d-beb2-bcc0bdc13a7d@intel.com> (raw)
In-Reply-To: <20261007215650.159871-1-tiwai@suse.de>
On 10/7/2026 11:56 PM, Takashi Iwai wrote:
> Here is another series of small fixes for HD-audio, beginning with the
> fix for an issue reported by Sashiko, and extended the fixes to ASoC
> HD-audio and a potential improvement that were spotted during the
> development of the first patch.
>
>
> Takashi
>
> ===
>
> Takashi Iwai (3):
> ALSA: hda: Stop unsol events and jack polling before codec unbind
> ASoC: codecs: hda: Stop unsol events and jack polling before codec
> removal
> ALSA: hda: Make hdac_device.registered a plain bool
Thank you for fixing the ASoC's hda-driver too. The first two patches
I've reviewed thoroughly, look good. The third is something I can learn
from.
Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
prev parent reply other threads:[~2026-10-09 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 21:56 [PATCH 0/3] ALSA/ASoC: hda: Fix race between unsol events and unbind Takashi Iwai
2026-10-07 21:56 ` [PATCH 1/3] ALSA: hda: Stop unsol events and jack polling before codec unbind Takashi Iwai
2026-10-08 9:08 ` Cezary Rojewski
2026-10-08 10:16 ` Takashi Iwai
2026-10-08 11:52 ` Cezary Rojewski
2026-10-08 12:01 ` Takashi Iwai
2026-10-07 21:56 ` [PATCH 2/3] ASoC: codecs: hda: Stop unsol events and jack polling before codec removal Takashi Iwai
2026-10-07 21:56 ` [PATCH 3/3] ALSA: hda: Make hdac_device.registered a plain bool Takashi Iwai
2026-10-09 7:44 ` Cezary Rojewski [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=eba0472e-5bf0-471d-beb2-bcc0bdc13a7d@intel.com \
--to=cezary.rojewski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--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