From: "Danilo Krummrich" <dakr@kernel.org>
To: "Takashi Iwai" <tiwai@suse.de>
Cc: "Cássio Gabriel" <cassiogabrielcontato@gmail.com>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"Russ Weight" <russ.weight@linux.dev>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Takashi Iwai" <tiwai@suse.com>,
"Shenghao Ding" <shenghao-ding@ti.com>,
"Kevin Lu" <kevin-lu@ti.com>, "Baojun Xu" <baojun.xu@ti.com>,
"Jaroslav Kysela" <perex@perex.cz>,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v4 0/2] firmware_loader/ALSA: Fix TAS2781 async firmware teardown
Date: Wed, 06 May 2026 11:34:39 +0200 [thread overview]
Message-ID: <DIBHP03H2703.3GVN744LMKNQ1@kernel.org> (raw)
In-Reply-To: <874iklt12t.wl-tiwai@suse.de>
On Wed May 6, 2026 at 10:05 AM CEST, Takashi Iwai wrote:
> On Tue, 05 May 2026 13:18:15 +0200,
> Cássio Gabriel wrote:
>> Cássio Gabriel (2):
>> firmware_loader: Add cancel helper for async requests
>> ALSA: hda/tas2781: Cancel async firmware request at unbind
Looks good to me now.
> I guess this could go via driver tree? Or I can take both if I get an
> ack, too.
Sure, I can pick it up via the driver-core tree, but please also feel free to
take it through the sounds tree.
Acked-by: Danilo Krummrich <dakr@kernel.org>
> In anyway, for the series:
>
> Reviewed-by: Takashi Iwai <tiwai@suse.de>
next prev parent reply other threads:[~2026-05-06 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 11:18 [PATCH v4 0/2] firmware_loader/ALSA: Fix TAS2781 async firmware teardown Cássio Gabriel
2026-05-05 11:18 ` [PATCH v4 1/2] firmware_loader: Add cancel helper for async requests Cássio Gabriel
2026-05-05 11:18 ` [PATCH v4 2/2] ALSA: hda/tas2781: Cancel async firmware request at unbind Cássio Gabriel
2026-05-06 8:05 ` [PATCH v4 0/2] firmware_loader/ALSA: Fix TAS2781 async firmware teardown Takashi Iwai
2026-05-06 9:34 ` Danilo Krummrich [this message]
2026-05-06 11:14 ` Takashi Iwai
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=DIBHP03H2703.3GVN744LMKNQ1@kernel.org \
--to=dakr@kernel.org \
--cc=baojun.xu@ti.com \
--cc=cassiogabrielcontato@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=kevin-lu@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=perex@perex.cz \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=shenghao-ding@ti.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.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