From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Vinod Koul <vkoul@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the soundwire tree
Date: Thu, 3 Mar 2022 11:00:38 +0000 [thread overview]
Message-ID: <ef2bdf6e-37f8-46d8-fdd3-4e548104b52f@linaro.org> (raw)
In-Reply-To: <20220303215930.014e72f8@canb.auug.org.au>
Thanks Stephen,
On 03/03/2022 10:59, Stephen Rothwell wrote:
> Hi all,
>
> After merging the soundwire tree, today's linux-next build (s390
> allmodconfig) failed like this:
>
> drivers/soundwire/qcom.c:1460:12: error: 'swrm_runtime_resume' defined but not used [-Werror=unused-function]
>
> Caused by commit
>
> 74e79da9fd46 ("soundwire: qcom: add runtime pm support")
Fix patch is on the way.
--srini
>
next prev parent reply other threads:[~2022-03-03 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 10:59 linux-next: build failure after merge of the soundwire tree Stephen Rothwell
2022-03-03 11:00 ` Srinivas Kandagatla [this message]
2022-03-03 16:07 ` Vinod Koul
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=ef2bdf6e-37f8-46d8-fdd3-4e548104b52f@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vkoul@kernel.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