From: Mark Brown <broonie@kernel.org>
To: Jason Montleon <jmontleo@redhat.com>,
pierre-louis.bossart@linux.intel.com
Cc: oder_chiou@realtek.com, cezary.rojewski@intel.com,
ckeepax@opensource.cirrus.com, regressions@lists.linux.dev,
alsa-devel@alsa-project.org, tiwai@suse.com,
stable@vger.kernel.org
Subject: Re: [PATCH v4 1/2] ASoC: rt5514: fix legacy dai naming
Date: Fri, 04 Nov 2022 14:56:01 +0000 [thread overview]
Message-ID: <166757376119.346347.7384763439814980163.b4-ty@kernel.org> (raw)
In-Reply-To: <20221103144612.4431-1-jmontleo@redhat.com>
On Thu, 3 Nov 2022 10:46:11 -0400, Jason Montleon wrote:
> Starting with 6.0-rc1 these messages are logged and the sound card
> is unavailable. Adding legacy_dai_naming to the rt5514-spi causes
> it to function properly again.
>
> [ 16.928454] kbl_r5514_5663_max kbl_r5514_5663_max: ASoC: CPU DAI
> spi-PRP0001:00 not registered
> [ 16.928561] platform kbl_r5514_5663_max: deferred probe pending
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/2] ASoC: rt5514: fix legacy dai naming
commit: 392cc13c5ec72ccd6bbfb1bc2339502cc59dd285
[2/2] ASoC: rt5677: fix legacy dai naming
commit: a1dca8774faf3f77eb34fa0ac6f3e2b82290b1e4
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2022-11-04 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 14:46 [PATCH v4 1/2] ASoC: rt5514: fix legacy dai naming Jason Montleon
2022-11-03 14:46 ` [PATCH v4 2/2] ASoC: rt5677: " Jason Montleon
2022-11-03 15:07 ` Charles Keepax
2022-11-03 15:06 ` [PATCH v4 1/2] ASoC: rt5514: " Charles Keepax
2022-11-04 14:56 ` Mark Brown [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=166757376119.346347.7384763439814980163.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cezary.rojewski@intel.com \
--cc=ckeepax@opensource.cirrus.com \
--cc=jmontleo@redhat.com \
--cc=oder_chiou@realtek.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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