From: Thomas Gleixner <tglx@linutronix.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Why does callback irq_startup in struct irq_chip return _unsigned_ int ?
Date: Fri, 26 May 2017 09:13:06 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1705260910200.1902@nanos> (raw)
In-Reply-To: <a622b534-639e-a94e-8ea3-a52a49c37b6e@gmail.com>
Heiner,
On Thu, 25 May 2017, Heiner Kallweit wrote:
> 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?
/me scratches head.
IIRC then it was made unsigned int because that function cannot fail, but
can return that an interrupt was pending.
So if at all the thing should be 'bool'.
Thanks,
tglx
prev parent reply other threads:[~2017-05-26 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 21:28 Heiner Kallweit
2017-05-26 7:13 ` Thomas Gleixner [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=alpine.DEB.2.20.1705260910200.1902@nanos \
--to=tglx@linutronix.de \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®