Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: acelan.kao@canonical.com
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	Shuming Fan <shumingf@realtek.com>,
	Niranjan H Y <niranjan.hy@ti.com>,
	Maciej Strozek <mstrozek@opensource.cirrus.com>,
	Mac Chiang <mac.chiang@intel.corp-partner.google.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>,
	Miaoqian Lin <linmq006@gmail.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	broonie@kernel.org
Subject: Re: [PATCH] ASoC: sdw_utils: fix missing component_name for cs42l43 part_id 0x2A3B
Date: Mon, 15 Jun 2026 09:59:39 +0100	[thread overview]
Message-ID: <ai+++2m8HWB7F6eM@opensource.cirrus.com> (raw)
In-Reply-To: <178127688584.48375.17454457885369484858.b4-ty@b4>

On Fri, Jun 12, 2026 at 04:08:05PM +0100, Mark Brown wrote:
> On Wed, 10 Jun 2026 12:17:53 +0800, Chia-Lin Kao (AceLan) wrote:
> > ASoC: sdw_utils: fix missing component_name for cs42l43 part_id 0x2A3B
> 
> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-7.2
> 
> Thanks!
> 
> [1/1] ASoC: sdw_utils: fix missing component_name for cs42l43 part_id 0x2A3B
>       https://git.kernel.org/broonie/sound/c/c429fbea6174

Hi Chia-Lin Kao,

Did you get a bounce email for this patch from the Cirrus folks
and if so can I get a copy of that?

It seems we are all on it but none of us received the email. I am
assuming something went wrong in our email stack but if there was
a bounce would be excellent to have something to point our IT
people at.

Thanks,
Charles

      reply	other threads:[~2026-06-15  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  4:17 [PATCH] ASoC: sdw_utils: fix missing component_name for cs42l43 part_id 0x2A3B Chia-Lin Kao (AceLan)
2026-06-12 15:08 ` Mark Brown
2026-06-15  8:59   ` Charles Keepax [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=ai+++2m8HWB7F6eM@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=acelan.kao@canonical.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linmq006@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mac.chiang@intel.corp-partner.google.com \
    --cc=mstrozek@opensource.cirrus.com \
    --cc=niranjan.hy@ti.com \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=rf@opensource.cirrus.com \
    --cc=shumingf@realtek.com \
    --cc=tiwai@suse.com \
    --cc=yung-chuan.liao@linux.intel.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