From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/3] powerpc: fix comment in kernel/irq.c
Date: Wed, 24 Jan 2007 17:35:38 +1100 [thread overview]
Message-ID: <1169620538.18754.68.camel@localhost.localdomain> (raw)
In-Reply-To: <20061213123945.859071000@sipsolutions.net>>
On Wed, 2006-12-13 at 13:38 +0100, Johannes Berg wrote:
> plain text document attachment (irq-comment.patch)
> kernel/irq.c contains a comment that speaks of -1 and -2 as interrupt
> numbers, but this is actually dependent on configuration options now.
> Replace by NO_IRQ and NO_IRQ_ENABLED.
>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> --- linux-2.6-git.orig/arch/powerpc/kernel/irq.c 2006-12-13 12:03:44.406144791 +0100
> +++ linux-2.6-git/arch/powerpc/kernel/irq.c 2006-12-13 12:04:05.727144791 +0100
> @@ -281,10 +281,10 @@ void do_IRQ(struct pt_regs *regs)
>
> /*
> * Every platform is required to implement ppc_md.get_irq.
> - * This function will either return an irq number or -1 to
> + * This function will either return an irq number or NO_IRQ to
> * indicate there are no more pending.
> - * The value -2 is for buggy hardware and means that this IRQ
> - * has already been handled. -- Tom
> + * The value NO_IRQ_IGNORE is for buggy hardware and means that this
> + * IRQ has already been handled. -- Tom
> */
> irq = ppc_md.get_irq();
>
>
> --
prev parent reply other threads:[~2007-01-24 6:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 12:38 [PATCH 0/3] some preparations for suspend on G5 powermac Johannes Berg
2006-12-13 12:38 ` [PATCH 1/3] windfarm: dont die on suspend thread signal Johannes Berg
2007-01-24 6:32 ` Benjamin Herrenschmidt
2006-12-13 12:38 ` [PATCH 2/3] powermac: proper time of day after resume Johannes Berg
2007-01-24 6:34 ` Benjamin Herrenschmidt
2007-01-24 8:46 ` Johannes Berg
2007-01-24 8:51 ` Benjamin Herrenschmidt
2007-01-24 8:54 ` Gabriel Paubert
2007-01-24 9:32 ` Benjamin Herrenschmidt
2007-01-24 10:36 ` Gabriel Paubert
2007-01-24 14:23 ` Segher Boessenkool
2007-01-24 21:44 ` Benjamin Herrenschmidt
2007-01-24 22:24 ` Segher Boessenkool
2007-01-24 22:35 ` Benjamin Herrenschmidt
2007-01-24 23:21 ` Segher Boessenkool
2007-01-25 7:39 ` Michel Dänzer
2007-01-25 8:06 ` Benjamin Herrenschmidt
2007-01-25 8:10 ` Michel Dänzer
2007-01-25 11:09 ` Gabriel Paubert
2007-01-25 12:54 ` Johannes Berg
2007-01-26 14:35 ` Johannes Berg
2007-02-01 19:16 ` [PATCH] " Johannes Berg
2007-02-02 12:19 ` Johannes Berg
2007-02-03 2:41 ` Michael Ellerman
2007-02-03 17:37 ` Johannes Berg
2007-05-02 4:45 ` Paul Mackerras
2007-05-02 4:47 ` Paul Mackerras
2007-05-02 8:26 ` Johannes Berg
2007-05-02 14:25 ` [PATCH] powerpc timer sysdev: use mktime Johannes Berg
2007-05-23 15:28 ` Johannes Berg
2007-05-28 4:33 ` Paul Mackerras
2006-12-13 12:38 ` [PATCH 3/3] powerpc: fix comment in kernel/irq.c Johannes Berg
2006-12-13 13:13 ` Johannes Berg
2006-12-19 5:40 ` Paul Mackerras
2006-12-19 18:29 ` Johannes Berg
2007-01-24 6:35 ` Benjamin Herrenschmidt [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=1169620538.18754.68.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.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).