From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
"Mark Brown" <broonie@kernel.org>
Subject: [PATCH 0/2] ASoC: mt8183: Fixes from an initial glance at a kselftest run
Date: Sun, 26 Feb 2023 12:49:55 +0000 [thread overview]
Message-ID: <20230224-asoc-mt8183-quick-fixes-v1-0-041f29419ed5@kernel.org> (raw)
This is a collection of fixes I came up after glancing through an
initial test run with the snappily named Kukui Jacuzzi SKU16 Chromebook
on KernelCI. There are more issues flagged, this is just what I fixed
thus far.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
ASoC: mt8183: Remove spammy logging from I2S DAI driver
ASoC: mt8183: Fix event generation for I2S DAI operations
sound/soc/mediatek/mt8183/mt8183-dai-i2s.c | 21 +++------------------
1 file changed, 3 insertions(+), 18 deletions(-)
---
base-commit: d2980d8d826554fa6981d621e569a453787472f8
change-id: 20230224-asoc-mt8183-quick-fixes-ccb7c567c755
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2023-02-26 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 12:49 Mark Brown [this message]
2023-02-26 12:49 ` [PATCH 1/2] ASoC: mt8183: Remove spammy logging from I2S DAI driver Mark Brown
2023-02-27 8:55 ` AngeloGioacchino Del Regno
2023-02-26 12:49 ` [PATCH 2/2] ASoC: mt8183: Fix event generation for I2S DAI operations Mark Brown
2023-02-27 8:55 ` AngeloGioacchino Del Regno
2023-02-28 18:00 ` [PATCH 0/2] ASoC: mt8183: Fixes from an initial glance at a kselftest run 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=20230224-asoc-mt8183-quick-fixes-v1-0-041f29419ed5@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.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=nfraprado@collabora.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®