From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Dimitris Papastamos <dp@opensource.wolfsonmicro.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Mihai Serban <mihai.serban@gmail.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] ASoC: dapm: improve debugfs output and introduce dapm-graph
Date: Mon, 22 Apr 2024 17:09:08 +0900 [thread overview]
Message-ID: <171377334868.1755143.5418794002755398989.b4-ty@kernel.org> (raw)
In-Reply-To: <20240416-vizdapm-ng-v1-0-5d33c0b57bc5@bootlin.com>
On Tue, 16 Apr 2024 08:00:23 +0200, Luca Ceresoli wrote:
> This patch series improves the tools available to understand and debug
> DAPM.
>
> Patches 1-2 add more information to the widget files exposed in debugfs.
>
> Patch 3 introduces dapm-graph, a script to generate a picture of the DAPM
> state inspired to vizdapm.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: dapm: debugfs: add component to route lines
commit: cbd9eed87107bb6d6e537e79aeea65399898ca41
[2/3] ASoC: dapm: debugfs: show the widget type
commit: 5b1047dcf80b35bafcacbd10b57342d1a96139c0
[3/3] tools/sound/dapm-graph: new tool to visualize DAPM state
commit: e7bb43898bcf54da7ffb4819a04c8428f7db24db
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-22 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 6:00 [PATCH 0/3] ASoC: dapm: improve debugfs output and introduce dapm-graph Luca Ceresoli
2024-04-16 6:00 ` [PATCH 1/3] ASoC: dapm: debugfs: add component to route lines Luca Ceresoli
2024-04-16 6:00 ` [PATCH 2/3] ASoC: dapm: debugfs: show the widget type Luca Ceresoli
2024-04-16 6:00 ` [PATCH 3/3] tools/sound/dapm-graph: new tool to visualize DAPM state Luca Ceresoli
2024-04-16 23:37 ` [PATCH 0/3] ASoC: dapm: improve debugfs output and introduce dapm-graph Alexandre Belloni
2024-04-22 8:09 ` 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=171377334868.1755143.5418794002755398989.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=dp@opensource.wolfsonmicro.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mihai.serban@gmail.com \
--cc=perex@perex.cz \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).