From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix compile failure on PA-RISC
Date: Sun, 6 May 2012 13:24:13 +0100 [thread overview]
Message-ID: <20120506132413.28499956@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1205051448400.2623@file.rdu.redhat.com>
> What NO_IRQ problem do you mean? There is
> #define NO_IRQ (-1)
> in arch/parisc/include/asm/irq.h.
It should be zero ready for us to get rid of it. Aa far as I can tell
pa-risc can just move to 0 without anything breaking. In fact some stuff
like serial port polling on 8250 ports will begin to work if it's done.
> And there are other NO_IRQ definitions in other architectures, some
> defining it to ((unsigned int)(-1)), some to 0xffffffff, some to INT_MAX,
> some to (-1) and some to (0).
Yes people are working on removing them all.
Alan
next prev parent reply other threads:[~2012-05-06 12:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 2:58 [PATCH] Fix compile failure on PA-RISC Mikulas Patocka
2012-05-05 3:04 ` [PATCH] Revert 5dd5bc40f3b6e0ccdaad948dbadc94ad0906cb25 Mikulas Patocka
2012-05-05 7:39 ` Jiri Slaby
2012-05-05 18:44 ` Mikulas Patocka
2012-05-05 20:49 ` [PATCH 1/1] TTY: pdc_cons, fix regression in close Jiri Slaby
2012-05-05 6:55 ` [PATCH] Fix compile failure on PA-RISC Rolf Eike Beer
2012-05-05 17:09 ` Linus Torvalds
2012-05-05 18:55 ` Mikulas Patocka
2012-05-05 20:09 ` John David Anglin
2012-05-05 21:24 ` Helge Deller
2012-05-06 7:57 ` James Bottomley
2012-05-05 10:58 ` Alan Cox
2012-05-05 18:53 ` Mikulas Patocka
2012-05-05 18:55 ` Linus Torvalds
2012-05-05 22:00 ` Rolf Eike Beer
2012-05-09 3:20 ` Mikulas Patocka
2012-05-09 12:01 ` Alan Cox
2012-05-09 17:51 ` Linus Torvalds
2012-05-10 9:24 ` Geert Uytterhoeven
2012-05-06 12:24 ` Alan Cox [this message]
2012-05-09 17:38 ` Grant Grundler
2012-05-10 11:40 ` Alan Cox
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=20120506132413.28499956@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=torvalds@linux-foundation.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).