From: Mark Brown <broonie@kernel.org>
To: "Martin Povišer" <povik+lin@cutebit.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Charles Keepax <ckeepax@opensource.cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: Re: [PATCH] ASoC: dapm: Export new 'graph.dot' file in debugfs
Date: Mon, 22 Aug 2022 14:04:19 +0100 [thread overview]
Message-ID: <YwN+0yHSOSC2aD+J@sirena.org.uk> (raw)
In-Reply-To: <3234D74E-0DFF-4BB5-87ED-6135BAC1F31D@cutebit.org>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Mon, Aug 22, 2022 at 02:38:09PM +0200, Martin Povišer wrote:
> > On 22. 8. 2022, at 14:27, Mark Brown <broonie@kernel.org> wrote:
> > There was a tool floating about in the past (last copy I knew about was
> > on Wolfson's git but they took that down) - can we not just continue to
> > do that?
> I don’t know the tool or where would I find it. I think it’s neat
Copying in Charles and Richard who might know about the status of the
tool Dimitris wrote.
> simply having a ‘graph.dot’ at hand, especially since it requires
> little code. (Although sure there’s the danger of it growing.)
I'm also worried about people going in and wanting other more tool
specific formats adding, if we didn't have anything at all it'd be one
thing but we do have something.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-22 13:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:52 [PATCH] ASoC: dapm: Export new 'graph.dot' file in debugfs Martin Povišer
2022-08-22 12:27 ` Mark Brown
2022-08-22 12:34 ` Takashi Iwai
2022-08-22 12:47 ` Mark Brown
2022-08-22 12:38 ` Martin Povišer
2022-08-22 13:04 ` Mark Brown [this message]
2022-08-22 13:11 ` Martin Povišer
2022-08-22 16:10 ` Mark Brown
2022-08-25 13:11 ` Charles Keepax
2022-08-22 13:06 ` Pierre-Louis Bossart
2022-08-22 16:14 ` 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=YwN+0yHSOSC2aD+J@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=alyssa@rosenzweig.io \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=povik+lin@cutebit.org \
--cc=rf@opensource.cirrus.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