All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: "Stefan Binding (Opensource)" <sbinding@opensource.cirrus.com>,
	"'Cássio Gabriel'" <cassiogabrielcontato@gmail.com>,
	"'David Rhodes'" <david.rhodes@cirrus.com>,
	"'Richard Fitzgerald'" <rf@opensource.cirrus.com>,
	"'Takashi Iwai'" <tiwai@suse.com>,
	"'Vitaly Rodionov'" <vitalyr@opensource.cirrus.com>,
	"'Jaroslav Kysela'" <perex@perex.cz>,
	linux-sound@vger.kernel.org, patches@opensource.cirrus.com,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH RESEND] ALSA: hda/cs35l41: Fix firmware load work teardown
Date: Fri, 15 May 2026 17:56:28 +0200	[thread overview]
Message-ID: <878q9ksm37.wl-tiwai@suse.de> (raw)
In-Reply-To: <agdAlJek88n6K53H@opensource.cirrus.com>

On Fri, 15 May 2026 17:49:40 +0200,
Charles Keepax wrote:
> 
> On Fri, May 15, 2026 at 04:08:14PM +0100, Stefan Binding (Opensource) wrote:
> > > -----Original Message-----
> > > 
> > > @Stefan, could you also please have a look.
> > 
> > I think this is fine to do, and I did some tests to make sure it doesn’t
> > break anything.
> > Reviewed-by: Stefan Binding <sbinding@opensource.cirrus.com>
> 
> If Stefan is happy so I am :-)

OK, let's take it and see whether everything works.

As this doesn't look like a particularly urgent fix, I apply to
for-next branch for 7.2.


thanks,

Takashi

  reply	other threads:[~2026-05-15 15:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11  4:29 [PATCH RESEND] ALSA: hda/cs35l41: Fix firmware load work teardown Cássio Gabriel
2026-05-15  9:07 ` Takashi Iwai
2026-05-15 10:12 ` Charles Keepax
2026-05-15 15:08   ` Stefan Binding (Opensource)
2026-05-15 15:49     ` Charles Keepax
2026-05-15 15:56       ` Takashi Iwai [this message]
2026-05-15 16:02         ` Cássio Gabriel Monteiro Pires

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=878q9ksm37.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=cassiogabrielcontato@gmail.com \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=david.rhodes@cirrus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=rf@opensource.cirrus.com \
    --cc=sbinding@opensource.cirrus.com \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=vitalyr@opensource.cirrus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.