linux-kernel - Re: [sh] smp-shx3.c: error: ignoring return value of 'request_irq', declared with attribute warn_unused

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+G9fYtpsoKjHR3Fr-so4SFopMUH+5m=RR9py2Uc9NKTmvm5Eg@mail.gmail.com>
Date:   Mon, 4 Jan 2021 16:28:59 +0530
From:   Naresh Kamboju <naresh.kamboju@...aro.org>
To:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc:     open list <linux-kernel@...r.kernel.org>, linux-sh@...r.kernel.org,
        lkft-triage@...ts.linaro.org,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Rich Felker <dalias@...c.org>
Subject: Re: [sh] smp-shx3.c: error: ignoring return value of 'request_irq',
 declared with attribute warn_unused_result

On Fri, 1 Jan 2021 at 20:18, John Paul Adrian Glaubitz
<glaubitz@...sik.fu-berlin.de> wrote:
>
> Hello Naresh!
>
> On 12/9/20 6:26 PM, Naresh Kamboju wrote:
> > Linux next 20201209 tag the arch 'sh' defconfig build failed to build with
> > gcc-8, gcc-9 and gcc-10.
> >
> > arch/sh/kernel/cpu/sh4a/smp-shx3.c: In function 'shx3_prepare_cpus':
> > arch/sh/kernel/cpu/sh4a/smp-shx3.c:76:3: error: ignoring return value
> > of 'request_irq', declared with attribute warn_unused_result
> > [-Werror=unused-result]
> >    request_irq(104 + i, ipi_interrupt_handler,
> >    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >         IRQF_PERCPU, "IPI", (void *)(long)i);
> >         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > Reported-by: Naresh Kamboju <naresh.kamboju@...aro.org>
>
> I can't reproduce this issue on Linus' current tree as of today.
>
> Maybe the issue has been fixed in the meantime?

Seems like this has been fixed in the meantime.

- Naresh