From: Trevor Wu <trevor.wu@mediatek.com>
To: <pierre-louis.bossart@linux.intel.com>,
<peter.ujfalusi@linux.intel.com>,
<yung-chuan.liao@linux.intel.com>,
<ranjani.sridharan@linux.intel.com>,
<kai.vehmanen@linux.intel.com>, <daniel.baluta@nxp.com>,
<broonie@kernel.org>, <lgirdwood@gmail.com>, <tiwai@suse.com>,
<perex@perex.cz>, <matthias.bgg@gmail.com>,
<angelogioacchino.delregno@collabora.com>
Cc: <trevor.wu@mediatek.com>, <yc.hung@mediatek.com>,
<sound-open-firmware@alsa-project.org>,
<alsa-devel@alsa-project.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] ASoC: SOF: mediatek: remove unused variables
Date: Fri, 3 Nov 2023 17:54:29 +0800 [thread overview]
Message-ID: <20231103095433.10475-1-trevor.wu@mediatek.com> (raw)
There are some variables that are no longer being used because they
were declared for the deprecated memory layout. Currently, these code
sections confuse the users. Therefore, this series removes the code
that was implemented for those variables.
Trevor Wu (3):
ASoC: SOF: mediatek: mt8195: clean up unused code
ASoC: SOF: mediatek: mt8186: clean up unused code
ASoC: SOF: mediatek: remove unused variables
sound/soc/sof/mediatek/adsp_helper.h | 4 ---
sound/soc/sof/mediatek/mt8186/mt8186.c | 49 --------------------------
sound/soc/sof/mediatek/mt8195/mt8195.c | 49 --------------------------
3 files changed, 102 deletions(-)
--
2.18.0
next reply other threads:[~2023-11-03 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 9:54 Trevor Wu [this message]
2023-11-03 9:54 ` [PATCH 1/3] ASoC: SOF: mediatek: mt8195: clean up unused code Trevor Wu
2023-11-07 13:55 ` AngeloGioacchino Del Regno
2023-11-03 9:54 ` [PATCH 2/3] ASoC: SOF: mediatek: mt8186: " Trevor Wu
2023-11-07 13:55 ` AngeloGioacchino Del Regno
2023-11-03 9:54 ` [PATCH 3/3] ASoC: SOF: mediatek: remove unused variables Trevor Wu
2023-11-07 13:55 ` AngeloGioacchino Del Regno
2023-11-13 16:14 ` [PATCH 0/3] " 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=20231103095433.10475-1-trevor.wu@mediatek.com \
--to=trevor.wu@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.com \
--cc=yc.hung@mediatek.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®