From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Temitope obabi <obabitemitope765@gmail.com>, <broonie@kernel.org>
Cc: <liam.r.girdwood@linux.intel.com>,
<peter.ujfalusi@linux.intel.com>,
<yung-chuan.liao@linux.intel.com>, <kai.vehmanen@linux.intel.com>,
<rostedt@goodmis.org>, <mhiramat@kernel.org>,
<mathieu.desnoyers@efficios.com>, <linux-sound@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: Intel: Remove unused intel-sst.h trace header
Date: Tue, 17 Nov 2026 15:02:50 +0100 [thread overview]
Message-ID: <b1344127-25aa-45d4-8cee-756264231dfe@intel.com> (raw)
In-Reply-To: <2b41ca22-dc89-4e7c-8144-4dd6c02a5294@intel.com>
On 11/17/2026 3:00 PM, Cezary Rojewski wrote:
> On 11/17/2026 2:45 PM, Temitope obabi wrote:
>> Commit 970d299b0a0a ("ASoC: Intel: Remove unused code") removed
>> sound/soc/intel/common/sst-dsp.c, the only file that defined
>> CREATE_TRACE_POINTS and included trace/events/intel-sst.h.
>>
>> Nothing includes this header anymore, so none of its tracepoints are
>> built. Remove the unused header.
>>
>> Signed-off-by: Temitope obabi <obabitemitope765@gmail.com>
> What's going on here. There is already v2 of yours [1] which has been
> commented by me and Steven. Why are we having a separate thread for the
> exact same subject?
Meh, forgotten to add the link.
[1]:
https://lore.kernel.org/all/20261111223102.1310-1-obabitemitope765@gmail.com/
prev parent reply other threads:[~2026-11-17 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 13:45 [PATCH] ASoC: Intel: Remove unused intel-sst.h trace header Temitope obabi
2026-11-17 14:00 ` Cezary Rojewski
2026-11-17 14:02 ` Cezary Rojewski [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=b1344127-25aa-45d4-8cee-756264231dfe@intel.com \
--to=cezary.rojewski@intel.com \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=obabitemitope765@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=rostedt@goodmis.org \
--cc=yung-chuan.liao@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.