From: Simon Trimmer <simont@opensource.cirrus.com>
To: <tiwai@suse.com>
Cc: <linux-sound@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>,
<soyer@irl.hu>, <shenghao-ding@ti.com>, <kevin-lu@ti.com>,
<baojun.xu@ti.com>, Simon Trimmer <simont@opensource.cirrus.com>
Subject: [PATCH 0/3] ALSA: hda: Component should be unbound before deconstruction
Date: Thu, 13 Jun 2024 14:37:10 +0100 [thread overview]
Message-ID: <20240613133713.75550-1-simont@opensource.cirrus.com> (raw)
Small chain of fixes to correct hda drivers using the hda component
infrastructure so that they unregister their component before proceeding
to deconstruct the driver.
These three patches been separated from the chain "[PATCH v2 0/7] ALSA:
hda: Improvements to hda_component"
Simon Trimmer (3):
ALSA: hda: cs35l56: Component should be unbound before deconstruction
ALSA: hda: cs35l41: Component should be unbound before deconstruction
ALSA: hda: tas2781: Component should be unbound before deconstruction
sound/pci/hda/cs35l41_hda.c | 4 ++--
sound/pci/hda/cs35l56_hda.c | 4 ++--
sound/pci/hda/tas2781_hda_i2c.c | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
--
2.34.1
next reply other threads:[~2024-06-13 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 13:37 Simon Trimmer [this message]
2024-06-13 13:37 ` [PATCH 1/3] ALSA: hda: cs35l56: Component should be unbound before deconstruction Simon Trimmer
2024-06-13 13:37 ` [PATCH 2/3] ALSA: hda: cs35l41: " Simon Trimmer
2024-06-13 13:37 ` [PATCH 3/3] ALSA: hda: tas2781: " Simon Trimmer
2024-06-14 12:52 ` [PATCH 0/3] ALSA: hda: " 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=20240613133713.75550-1-simont@opensource.cirrus.com \
--to=simont@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=baojun.xu@ti.com \
--cc=kevin-lu@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=shenghao-ding@ti.com \
--cc=soyer@irl.hu \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox