From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>,
James Schulman <james.schulman@cirrus.com>,
David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
Lee Jones <lee@kernel.org>,
Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
regressions@lists.linux.dev
Subject: Re: mainline build failure due to ace6d1448138 ("mfd: cs42l43: Add support for cs42l43 core driver")
Date: Wed, 30 Aug 2023 15:11:51 +0200 [thread overview]
Message-ID: <6c272652-9689-4826-6e84-8aa23086c6ac@leemhuis.info> (raw)
In-Reply-To: <ZO8oNb2hpegB6BbE@debian>
On 30.08.23 13:29, Sudip Mukherjee (Codethink) wrote:
>
> The latest mainline kernel branch fails to build alpha, csky and s390
> allmodconfig with the error:
Thx for the report and involving regzbot.
FWIW, 0day bot noticed this earlier and Charles Keepax (now CCed) afaics
even submitted a fix a bit more than a week ago, but that didn't get any
further it seems:
https://lore.kernel.org/all/202308212225.fGjY1rr6-lkp@intel.com/
https://lore.kernel.org/all/20230822114914.340359-1-ckeepax@opensource.cirrus.com/
Ciao, Thorsten
> drivers/mfd/cs42l43.c:1138:12: error: 'cs42l43_runtime_resume' defined but not used [-Werror=unused-function]
> 1138 | static int cs42l43_runtime_resume(struct device *dev)
> | ^~~~~~~~~~~~~~~~~~~~~~
> drivers/mfd/cs42l43.c:1124:12: error: 'cs42l43_runtime_suspend' defined but not used [-Werror=unused-function]
> 1124 | static int cs42l43_runtime_suspend(struct device *dev)
> | ^~~~~~~~~~~~~~~~~~~~~~~
> drivers/mfd/cs42l43.c:1106:12: error: 'cs42l43_resume' defined but not used [-Werror=unused-function]
> 1106 | static int cs42l43_resume(struct device *dev)
> | ^~~~~~~~~~~~~~
> drivers/mfd/cs42l43.c:1076:12: error: 'cs42l43_suspend' defined but not used [-Werror=unused-function]
> 1076 | static int cs42l43_suspend(struct device *dev)
> | ^~~~~~~~~~~~~~~
>
> git bisect pointed to ace6d1448138 ("mfd: cs42l43: Add support for cs42l43 core driver")
>
> I will be happy to test any patch or provide any extra log if needed.
P.S.:
#regzbot monitor:
https://lore.kernel.org/all/20230822114914.340359-1-ckeepax@opensource.cirrus.com/
#regzbot monitor:
https://lore.kernel.org/all/202308212225.fGjY1rr6-lkp@intel.com/
#regzbot fix: mfd: cs42l43: Use correct macro for new-style PM runtime ops
next prev parent reply other threads:[~2023-08-30 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 11:29 mainline build failure due to ace6d1448138 ("mfd: cs42l43: Add support for cs42l43 core driver") Sudip Mukherjee (Codethink)
2023-08-30 13:09 ` Takashi Iwai
2023-08-30 15:00 ` Charles Keepax
2023-08-30 15:12 ` Takashi Iwai
2023-08-30 13:11 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-09-23 15:02 ` Sudip Mukherjee
2023-09-24 7:58 ` Thorsten Leemhuis
2023-09-24 8:05 ` Thorsten Leemhuis
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=6c272652-9689-4826-6e84-8aa23086c6ac@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=david.rhodes@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=regressions@lists.linux.dev \
--cc=rf@opensource.cirrus.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).