From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Komal Bajaj <quic_kbajaj@quicinc.com>,
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 nvmem tree
Date: Mon, 21 Aug 2023 09:48:45 +1000 [thread overview]
Message-ID: <20230821094845.440c96b2@canb.auug.org.au> (raw)
In-Reply-To: <20230815202508.0523ecce@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 669 bytes --]
Hi all,
On Tue, 15 Aug 2023 20:25:08 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the nvmem tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/nvmem/sec-qfprom.c: In function 'sec_qfprom_probe':
> drivers/nvmem/sec-qfprom.c:59:13: error: unused variable 'ret' [-Werror=unused-variable]
> 59 | int ret;
> | ^~~
> cc1: all warnings being treated as errors
>
> Caused by commit
>
> 9c7f2bce8a0e ("nvmem: sec-qfprom: Add Qualcomm secure QFPROM support")
>
> I have used the nvmem tree from next-20230809 for today.
Ping?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-20 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 10:25 linux-next: build failure after merge of the nvmem tree Stephen Rothwell
2023-08-20 23:48 ` Stephen Rothwell [this message]
2023-08-21 5:27 ` Komal Bajaj
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 5:49 Stephen Rothwell
2023-12-11 10:23 ` Srinivas Kandagatla
2023-12-11 10:30 ` Miquel Raynal
2023-12-11 11:10 ` Srinivas Kandagatla
2023-12-11 13:53 ` Miquel Raynal
2022-11-01 3:21 Stephen Rothwell
2022-11-01 7:27 ` Srinivas Kandagatla
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=20230821094845.440c96b2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=quic_kbajaj@quicinc.com \
--cc=srinivas.kandagatla@linaro.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).