From: Marc Zyngier <maz@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-mips@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkft-triage@lists.linaro.org
Subject: Re: mips: irq.c:114:19: error: unused variable 'desc' [-Werror=unused-variable]
Date: Thu, 28 Oct 2021 14:50:40 +0100 [thread overview]
Message-ID: <c65bccca4fa1345e18942ff66675296d@kernel.org> (raw)
In-Reply-To: <CA+G9fYtQCd4V9Y=qEGZeQw17TRNG1p_g9MKtYaWVo8QPua-Cug@mail.gmail.com>
On 2021-10-28 12:47, Naresh Kamboju wrote:
> Regression found on mips gcc-10 built with defconfig
> Following build warnings / errors reported on linux next 20211027.
>
> The bisect tool pointing to the following commit
> The first bad commit:
>
> commit 4cb6f4df976b288aa02bbb658d38e73d34d8231f
> irq: mips: simplify do_domain_IRQ()
>
> metadata:
> git_describe: next-20211027
> git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> git_short_log: ae5179317e79 (\"Add linux-next specific files for
> 20211027\")
> target_arch: mips
> toolchain: gcc-10
>
> build error :
> --------------
> <stdin>:1559:2: warning: #warning syscall futex_waitv not implemented
> [-Wcpp]
> arch/mips/kernel/irq.c: In function 'do_domain_IRQ':
> arch/mips/kernel/irq.c:114:19: error: unused variable 'desc'
> [-Werror=unused-variable]
> struct irq_desc *desc;
> ^~~~
> cc1: all warnings being treated as errors
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Already fixed as of 20211028095652.3503790-1-siyanteng@loongson.cn
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2021-10-28 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 11:47 mips: irq.c:114:19: error: unused variable 'desc' [-Werror=unused-variable] Naresh Kamboju
2021-10-28 13:50 ` Marc Zyngier [this message]
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=c65bccca4fa1345e18942ff66675296d@kernel.org \
--to=maz@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mark.rutland@arm.com \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.