From: Takashi Iwai <tiwai@suse.de>
To: Simon Trimmer <simont@opensource.cirrus.com>
Cc: <tiwai@suse.com>, <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>
Subject: Re: [PATCH v3 0/4] ALSA: hda: Improvements to hda_component
Date: Tue, 18 Jun 2024 11:53:02 +0200 [thread overview]
Message-ID: <87le327f29.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240617154105.108635-1-simont@opensource.cirrus.com>
On Mon, 17 Jun 2024 17:41:01 +0200,
Simon Trimmer wrote:
>
> This series of patches moves duplicated members from the
> instanced component structures into a new parent structure and
> introduces locking so that consumers of the interface do not use
> stale data.
>
> Changes in v3:
> - These Fixes separated from this series to make them easier
> to manage:
> https://lore.kernel.org/all/20240613133713.75550-1-simont@opensource.cirrus.com/
>
> Simon Trimmer (4):
> ALSA: hda: hda_component: Introduce component parent structure
> ALSA: hda: hda_component: Change codecs to use component parent structure
> ALSA: hda: hda_component: Move codec field into the parent
> ALSA: hda: hda_component: Protect shared data with a mutex
Applied all patches now to for-next branch. Thanks.
Takashi
prev parent reply other threads:[~2024-06-18 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 15:41 [PATCH v3 0/4] ALSA: hda: Improvements to hda_component Simon Trimmer
2024-06-17 15:41 ` [PATCH 1/4] ALSA: hda: hda_component: Introduce component parent structure Simon Trimmer
2024-06-17 15:41 ` [PATCH 2/4] ALSA: hda: hda_component: Change codecs to use " Simon Trimmer
2024-06-17 15:41 ` [PATCH 3/4] ALSA: hda: hda_component: Move codec field into the parent Simon Trimmer
2024-06-17 15:41 ` [PATCH 4/4] ALSA: hda: hda_component: Protect shared data with a mutex Simon Trimmer
2024-06-18 9:53 ` Takashi Iwai [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=87le327f29.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--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=simont@opensource.cirrus.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