From: Mark Brown <broonie@kernel.org>
To: Matthew Schwartz <matthew.schwartz@linux.dev>
Cc: Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>, Sen Wang <sen@ti.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] ASoC: tas2783-sdw: use the BIOS speaker ID in the firmware name
Date: Mon, 2 Nov 2026 23:59:09 +0000 [thread overview]
Message-ID: <d01ea9df-e5bc-404e-91b0-802c27c103fb@sirena.org.uk> (raw)
In-Reply-To: <b501e25d-022d-4f37-88f6-f82af3d101ff@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Mon, Nov 02, 2026 at 03:54:12PM -0800, Matthew Schwartz wrote:
> On 11/2/26 3:46 PM, Mark Brown wrote:
> > Mixing this in with the fallback decision seems confusing. There's some
> > cases generated in the Sashiko review which look plausible though I
> > didn't fully work through everything:
> > https://sashiko.dev/#/patchset/20261016232416.2628603-1-matthew.schwartz%40linux.dev
> Thanks, didn't know Sashiko feedback wasn't in-line anymore. I'll take a look and send out a v2.
It's per subsystem opt in if it sends emails. TBH I prefer not to send
it directly since errors can end up confusing less experienced
submitters, and it's not appropriate for people to spend time fixing
detail issues if there's structural issues but those mostly need human
review.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-11-02 23:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 23:24 [PATCH 0/5] ASoC: support the ASUS ROG Xbox Ally X20 audio Matthew Schwartz
2026-10-16 23:24 ` [PATCH 1/5] ASoC: amd: acp-config: force SoundWire probe on ASUS RC74XA Matthew Schwartz
2026-10-19 5:40 ` Mukunda,Vijendar
2026-10-16 23:24 ` [PATCH 2/5] ASoC: amd: acp: add ACP70 SoundWire machine entry for " Matthew Schwartz
2026-10-19 5:41 ` Mukunda,Vijendar
2026-10-16 23:24 ` [PATCH 3/5] ASoC: tas2783-sdw: use the BIOS speaker ID in the firmware name Matthew Schwartz
2026-11-02 23:46 ` Mark Brown
2026-11-02 23:54 ` Matthew Schwartz
2026-11-02 23:59 ` Mark Brown [this message]
2026-10-16 23:24 ` [PATCH 4/5] ASoC: sdw_utils: honor empty DisCo port lists when creating DAI links Matthew Schwartz
2026-10-29 3:35 ` Mukunda,Vijendar
2026-11-02 23:46 ` Mark Brown
2026-10-16 23:24 ` [PATCH 5/5] ASoC: rt721-sdca: wait for PDEs to reach PS0 after powering them up Matthew Schwartz
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=d01ea9df-e5bc-404e-91b0-802c27c103fb@sirena.org.uk \
--to=broonie@kernel.org \
--cc=baojun.xu@ti.com \
--cc=kevin-lu@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=matthew.schwartz@linux.dev \
--cc=perex@perex.cz \
--cc=sen@ti.com \
--cc=shenghao-ding@ti.com \
--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
all inboxes | Powered by JetHome®