From: Mark Brown <broonie@kernel.org>
To: linux-sound@vger.kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de
Subject: Re: [PATCH 0/3] ASoC: SOF: misc fixes
Date: Wed, 10 Apr 2024 00:34:10 +0100 [thread overview]
Message-ID: <171270565002.199334.309648974862019777.b4-ty@kernel.org> (raw)
In-Reply-To: <20240408194147.28919-1-pierre-louis.bossart@linux.intel.com>
On Mon, 08 Apr 2024 14:41:44 -0500, Pierre-Louis Bossart wrote:
> We somehow missed the default path for DSP libraries for LNL, and need
> to restrict support for D0i3 w/ IPC4. Also add debugfs support for
> firmware profile information so that sof-test scripts can show what is
> being tested.
>
> Pierre-Louis Bossart (2):
> ASoC: SOF: Intel: add default firmware library path for LNL
> ASoC: SOF: debug: show firmware/topology prefix/names
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: SOF: Intel: add default firmware library path for LNL
commit: 305539a25a1c9929b058381aac6104bd939c0fee
[2/3] ASoC: SOF: pcm: Restrict DSP D0i3 during S0ix to IPC3
commit: 90a2353080eedec855d63f6aadfda14104ee9b06
[3/3] ASoC: SOF: debug: show firmware/topology prefix/names
commit: 17f4041244e66a417c646c8a90bc6747d5f1de1e
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:[~2024-04-09 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 19:41 [PATCH 0/3] ASoC: SOF: misc fixes Pierre-Louis Bossart
2024-04-08 19:41 ` [PATCH 1/3] ASoC: SOF: Intel: add default firmware library path for LNL Pierre-Louis Bossart
2024-04-08 19:41 ` [PATCH 2/3] ASoC: SOF: pcm: Restrict DSP D0i3 during S0ix to IPC3 Pierre-Louis Bossart
2024-04-08 19:41 ` [PATCH 3/3] ASoC: SOF: debug: show firmware/topology prefix/names Pierre-Louis Bossart
2024-04-09 23:34 ` 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=171270565002.199334.309648974862019777.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-sound@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).