linux-kernel - Why does callback irq_startup in struct irq_chip return _unsigned

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-next>] [day] [month] [year] [list]

Date:   Thu, 25 May 2017 23:28:07 +0200
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Why does callback irq_startup in struct irq_chip return _unsigned_
 int ?

Hi Thomas,

just by chance I noticed that callback irq_startup in struct irq_chip
returns an unsigned int.
This doesn't seem to make sense as the result is a normal retval which
is casted to a signed int in function irq_startup() anyway.

Is there any specific reason for this or is it simply a bug?

Rgds, Heiner