From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Benson Leung <bleung@google.com>,
Jarkko Nikula <jarkko.nikula@intel.com>
Subject: Re: [PATCHv2 4/5] ASoC: Intel: Add trace support for generic SST IPC messages.
Date: Tue, 18 Feb 2014 08:52:12 +0000 [thread overview]
Message-ID: <1392713532.2304.15.camel@loki> (raw)
In-Reply-To: <20140218013618.GW2669@sirena.org.uk>
On Tue, 2014-02-18 at 10:36 +0900, Mark Brown wrote:
> On Mon, Feb 17, 2014 at 01:32:09PM +0000, Liam Girdwood wrote:
>
> > include/trace/events/sst.h | 148 +++++++++++++++++++++++++++++++++++++++++++++
>
> intel-sst perhaps? It just seems like something someone else might use
> as a name.
True, it's a little generic. I also have trace/events/hswadsp.h for
Haswell IPC but that's quite specific so should be OK.
Liam
next prev parent reply other threads:[~2014-02-18 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 13:32 [PATCHv2 1/5] ASoC: Intel: Add Intel SST audio DSP low level shim driver Liam Girdwood
2014-02-17 13:32 ` [PATCHv2 2/5] ASoC: Intel: Add common SST driver loader on ACPI systems Liam Girdwood
2014-02-17 13:32 ` [PATCHv2 3/5] ASoC: Intel: Add Intel SST audio DSP Firmware loader Liam Girdwood
2014-02-17 13:48 ` Takashi Iwai
2014-02-17 16:49 ` Liam Girdwood
2014-02-18 1:44 ` Mark Brown
2014-02-18 1:35 ` Mark Brown
2014-02-18 8:47 ` Liam Girdwood
2014-02-17 13:32 ` [PATCHv2 4/5] ASoC: Intel: Add trace support for generic SST IPC messages Liam Girdwood
2014-02-18 1:36 ` Mark Brown
2014-02-18 8:52 ` Liam Girdwood [this message]
2014-02-18 9:34 ` Takashi Iwai
2014-02-17 13:32 ` [PATCHv2 5/5] ASoC: Intel: Add build support for Intel SST DSP core Liam Girdwood
2014-02-17 17:33 ` [PATCHv2 1/5] ASoC: Intel: Add Intel SST audio DSP low level shim driver Vinod Koul
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=1392713532.2304.15.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bleung@google.com \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@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