From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: "Chia-Lin Kao (AceLan)" <acelan.kao@canonical.com>,
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: Wed, 17 Jun 2026 09:14:19 +0100 [thread overview]
Message-ID: <ajJXW1c6NU3SljGr@opensource.cirrus.com> (raw)
In-Reply-To: <ajISWtufxlriqFP7@acelan-Precision-5480>
On Wed, Jun 17, 2026 at 11:22:50AM +0800, Chia-Lin Kao (AceLan) wrote:
> On Mon, Jun 15, 2026 at 09:59:39AM +0100, Charles Keepax wrote:
> > 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:
> > Did you get a bounce email for this patch from the Cirrus folks
> > and if so can I get a copy of that?
> I did get some bounce emails, but none of them are from cirrus.
> Maybe the email has been dropped silently.
>
> And if this is the issue, I doubt you will receive this email.
Interestingly I did get this one :-) Thanks for checking will
keep chasing the IT people at this end.
Thanks,
Charles
prev parent reply other threads:[~2026-06-17 8:15 UTC|newest]
Thread overview: 5+ 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
2026-06-17 3:22 ` Chia-Lin Kao (AceLan)
2026-06-17 8:14 ` 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=ajJXW1c6NU3SljGr@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