public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	<kailang@realtek.com>
Subject: Re: [PATCH v2 0/7] ALSA: hda: Improvements to hda_component
Date: Thu, 13 Jun 2024 14:06:00 +0200	[thread overview]
Message-ID: <87h6dxnj2v.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240603103524.32442-1-simont@opensource.cirrus.com>

On Mon, 03 Jun 2024 12:35:17 +0200,
Simon Trimmer wrote:
> 
> This series of patches makes sure that the existing consumers of
> the infrastructure unbind their interface before they begin
> destroying the driver, 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.
> 
> v2:
>  - Correct application of sizeof to pointer flagged by kernel test robot
> 
> Simon Trimmer (7):
>   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
>   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

The first three patches look rather like independent fixes.
Could you split those out and add proper Fixes tags, so that stable
trees can pick up?

The rest are a code refactoring and additional protection of the
mutex.


thanks,

Takashi

>  sound/pci/hda/cs35l41_hda.c     | 47 ++++++++++++---------
>  sound/pci/hda/cs35l56_hda.c     | 29 +++++++------
>  sound/pci/hda/hda_component.c   | 75 ++++++++++++++++++++-------------
>  sound/pci/hda/hda_component.h   | 48 ++++++++++++++-------
>  sound/pci/hda/patch_realtek.c   | 17 ++++----
>  sound/pci/hda/tas2781_hda_i2c.c | 37 ++++++++--------
>  6 files changed, 147 insertions(+), 106 deletions(-)
> 
> -- 
> 2.34.1
> 

      parent reply	other threads:[~2024-06-13 12:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 10:35 [PATCH v2 0/7] ALSA: hda: Improvements to hda_component Simon Trimmer
2024-06-03 10:35 ` [PATCH 1/7] ALSA: hda: cs35l56: Component should be unbound before deconstruction Simon Trimmer
2024-06-03 10:35 ` [PATCH 2/7] ALSA: hda: cs35l41: " Simon Trimmer
2024-06-03 10:35 ` [PATCH 3/7] ALSA: hda/tas2781: " Simon Trimmer
2024-06-03 10:35 ` [PATCH 4/7] ALSA: hda: hda_component: Introduce component parent structure Simon Trimmer
2024-06-03 10:35 ` [PATCH 5/7] ALSA: hda: hda_component: Change codecs to use " Simon Trimmer
2024-06-03 10:35 ` [PATCH 6/7] ALSA: hda: hda_component: Move codec field into the parent Simon Trimmer
2024-06-03 10:35 ` [PATCH 7/7] ALSA: hda: hda_component: Protect shared data with a mutex Simon Trimmer
2024-06-13 12:06 ` 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=87h6dxnj2v.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=baojun.xu@ti.com \
    --cc=kailang@realtek.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