From: Nathan Chancellor <nathan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Alexandre Mergnat <amergnat@baylibre.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 0/7] ASoC: mt8365: Fix -Werror builds
Date: Mon, 9 Sep 2024 08:48:39 -0700 [thread overview]
Message-ID: <20240909154839.GA59917@thelio-3990X> (raw)
In-Reply-To: <20240907-asoc-fix-mt8365-build-v1-0-7ad0bac20161@kernel.org>
On Sat, Sep 07, 2024 at 01:53:25AM +0100, Mark Brown wrote:
> Nathan reported that the newly added mt8365 drivers were causing a
> number of warnings which break -Werror builds, these were only visible
> on arm64 since the drivers did not have COMPILE_TEST enabled. Fix this
> and some other minor stuff I noticed while doing so.
> ---
> Mark Brown (7):
> ASoC: mt8365: Open code BIT() to avoid spurious warnings
> ASoC: mt8365: Remove spurious unsigned long casts
> ASoC: mt8365: Remove unused prototype for mt8365_afe_clk_group_48k()
> ASoC: mt8365: Make non-exported functions static
> ASoC: mt8365: Remove unused variables
> ASoC: mt8365: Remove unused DMIC IIR coefficient configuration
> ASoC: mt8365: Allow build coverage
Thanks for this. It appears to resolve all the issues from a build of
allmodconfig for arm, arm64, and x86.
Tested-by: Nathan Chancellor <nathan@kernel.org> # build
Cheers,
Nathan
next prev parent reply other threads:[~2024-09-09 15:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 0:53 Mark Brown
2024-09-07 0:53 ` [PATCH 1/7] ASoC: mt8365: Open code BIT() to avoid spurious warnings Mark Brown
2024-09-09 12:50 ` Alexandre Mergnat
2024-09-07 0:53 ` [PATCH 2/7] ASoC: mt8365: Remove spurious unsigned long casts Mark Brown
2024-09-09 11:50 ` AngeloGioacchino Del Regno
2024-09-09 12:51 ` Alexandre Mergnat
2024-09-07 0:53 ` [PATCH 3/7] ASoC: mt8365: Remove unused prototype for mt8365_afe_clk_group_48k() Mark Brown
2024-09-09 11:50 ` AngeloGioacchino Del Regno
2024-09-09 12:51 ` Alexandre Mergnat
2024-09-07 0:53 ` [PATCH 4/7] ASoC: mt8365: Make non-exported functions static Mark Brown
2024-09-09 11:50 ` AngeloGioacchino Del Regno
2024-09-09 12:52 ` Alexandre Mergnat
2024-09-07 0:53 ` [PATCH 5/7] ASoC: mt8365: Remove unused variables Mark Brown
2024-09-09 11:50 ` AngeloGioacchino Del Regno
2024-09-09 12:52 ` Alexandre Mergnat
2024-09-07 0:53 ` [PATCH 6/7] ASoC: mt8365: Remove unused DMIC IIR coefficient configuration Mark Brown
2024-09-09 11:50 ` AngeloGioacchino Del Regno
2024-09-07 0:53 ` [PATCH 7/7] ASoC: mt8365: Allow build coverage Mark Brown
2024-09-09 11:49 ` AngeloGioacchino Del Regno
2024-09-09 13:01 ` Alexandre Mergnat
2024-09-09 12:47 ` [PATCH 0/7] ASoC: mt8365: Fix -Werror builds Alexandre Mergnat
2024-09-09 15:48 ` Nathan Chancellor [this message]
2024-09-09 21:57 ` 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=20240909154839.GA59917@thelio-3990X \
--to=nathan@kernel.org \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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®