From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Nico Pache <npache@redhat.com>
Cc: broonie@kernel.org, patches@opensource.cirrus.com,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, simont@opensource.cirrus.com,
ckeepax@opensource.cirrus.com, brendan.higgins@linux.dev,
davidgow@google.com, rmoar@google.com, johannes.berg@intel.com,
sj@kernel.org
Subject: Re: [PATCH] kunit: cs_dsp: Depend on FW_CS_DSP rather then enabling it
Date: Sat, 22 Mar 2025 10:11:08 +0000 [thread overview]
Message-ID: <4cc16ecf-d498-44a6-99b2-eee840cff63d@opensource.cirrus.com> (raw)
In-Reply-To: <CAA1CXcD2RF6aXNH0ix=GN1+LTR9+dV7yRz-HGKZfUbSu+8ZM_w@mail.gmail.com>
On 20/3/25 17:35, Nico Pache wrote:
> Sorry links got mangled
>
Thanks. I'm on vacation right now but I'll take a look through
all those when I have time.
The unterminated string bugfix is this:
https://lore.kernel.org/all/20250211-cs_dsp-kunit-strings-v1-1-d9bc2035d154@linutronix.de/
I got lucky on all the UM, X86 and ARM builds I tested.
next prev parent reply other threads:[~2025-03-22 10:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 23:05 Nico Pache
2025-03-19 23:11 ` Nico Pache
2025-03-20 12:20 ` Richard Fitzgerald
2025-03-20 17:33 ` Nico Pache
2025-03-20 17:35 ` Nico Pache
2025-03-22 10:11 ` Richard Fitzgerald [this message]
2025-03-22 19:02 ` Richard Fitzgerald
2025-03-22 20:28 ` Richard Fitzgerald
2025-03-25 17:10 ` Mark Brown
2025-03-24 18:34 ` Nico Pache
2025-03-20 19:13 ` Mark Brown
2025-03-20 22:21 ` Nico Pache
2025-03-20 22:48 ` Mark Brown
2025-03-21 11:37 ` Nico Pache
2025-03-21 14:51 ` Mark Brown
2025-03-21 15:01 ` Nico Pache
2025-03-21 15:51 ` Mark Brown
2025-03-24 18:31 ` Nico Pache
2025-03-22 10:23 ` Richard Fitzgerald
2025-04-08 9:25 ` Richard Fitzgerald
2025-04-11 12:39 ` Richard Fitzgerald
2025-04-11 14:54 ` Nico Pache
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=4cc16ecf-d498-44a6-99b2-eee840cff63d@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=brendan.higgins@linux.dev \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=davidgow@google.com \
--cc=johannes.berg@intel.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=npache@redhat.com \
--cc=patches@opensource.cirrus.com \
--cc=rmoar@google.com \
--cc=simont@opensource.cirrus.com \
--cc=sj@kernel.org \
/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®