From: Nathan Chancellor <nathan@kernel.org>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: broonie@kernel.org, tiwai@suse.com, perex@perex.cz,
amadeuszx.slawinski@linux.intel.com, linux-sound@vger.kernel.org
Subject: Re: [PATCH 00/17] ASoC: Intel: avs: Adjust platform names
Date: Tue, 2 Sep 2025 14:20:25 -0700 [thread overview]
Message-ID: <20250902212025.GA2905120@ax162> (raw)
In-Reply-To: <20250902094853.1231842-1-cezary.rojewski@intel.com>
On Tue, Sep 02, 2025 at 11:48:36AM +0200, Cezary Rojewski wrote:
...
> - for the probe-board mach-context is dropped entirely. The panic [2] is
> gone
>
> [2]: https://lore.kernel.org/linux-sound/20250829225532.GA400117@ax162/
Can confirm, I applied this on top of next-20250902 and there was no
crash on boot.
Cheers,
Nathan
next prev parent reply other threads:[~2025-09-02 21:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 9:48 [PATCH 00/17] ASoC: Intel: avs: Adjust platform names Cezary Rojewski
2025-09-02 9:48 ` [PATCH 01/17] ASoC: Intel: avs: hda: Adjust platform name Cezary Rojewski
2025-09-02 9:48 ` [PATCH 02/17] ASoC: Intel: avs: da7219: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 03/17] ASoC: Intel: avs: dmic: Refactor dai_link creation Cezary Rojewski
2025-09-02 9:48 ` [PATCH 04/17] ASoC: Intel: avs: es8336: Adjust platform name Cezary Rojewski
2025-09-02 9:48 ` [PATCH 05/17] ASoC: Intel: avs: i2stest: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 06/17] ASoC: Intel: avs: max98357a: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 07/17] ASoC: Intel: avs: max98373: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 08/17] ASoC: Intel: avs: max98927: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 09/17] ASoC: Intel: avs: nau8825: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 10/17] ASoC: Intel: avs: probe: Refactor dai_link creation Cezary Rojewski
2025-09-02 9:48 ` [PATCH 11/17] ASoC: Intel: avs: rt274: Adjust platform name Cezary Rojewski
2025-09-02 9:48 ` [PATCH 12/17] ASoC: Intel: avs: rt286: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 13/17] ASoC: Intel: avs: rt298: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 14/17] ASoC: Intel: avs: rt5514: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 15/17] ASoC: Intel: avs: rt5663: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 16/17] ASoC: Intel: avs: rt5682: " Cezary Rojewski
2025-09-02 9:48 ` [PATCH 17/17] ASoC: Intel: avs: ssm4567: " Cezary Rojewski
2025-09-02 21:20 ` Nathan Chancellor [this message]
2025-09-03 10:58 ` [PATCH 00/17] ASoC: Intel: avs: Adjust platform names Mark Brown
2025-09-03 11:02 ` Amadeusz Sławiński
2025-09-03 18:53 ` Mark Brown
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=20250902212025.GA2905120@ax162 \
--to=nathan@kernel.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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