From: Ingo Molnar <mingo@elte.hu>
To: Olaf Hering <olaf@aepfle.de>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: [patch] genirq: clean up irq-flow-type naming, fix
Date: Wed, 18 Oct 2006 10:16:59 +0200 [thread overview]
Message-ID: <20061018081659.GA5778@elte.hu> (raw)
In-Reply-To: <20061018080411.GA13340@aepfle.de>
* Olaf Hering <olaf@aepfle.de> wrote:
> There is no prototype anymore, but still many users.
>
> a460e745e8f9c75a0525ff94154a0629f9d3e05d is likely the culprit:
> [PATCH] genirq: clean up irq-flow-type naming
oops, that was unintended. The patch below should fix this.
Ingo
--------------->
Subject: genirq: clean up irq-flow-type naming, fix
From: Ingo Molnar <mingo@elte.hu>
re-add the set_irq_chip_and_handler() prototype, it's still widely used.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
include/linux/irq.h | 3 +++
1 file changed, 3 insertions(+)
Index: linux/include/linux/irq.h
===================================================================
--- linux.orig/include/linux/irq.h
+++ linux/include/linux/irq.h
@@ -322,6 +322,9 @@ extern struct irq_chip no_irq_chip;
extern struct irq_chip dummy_irq_chip;
extern void
+set_irq_chip_and_handler(unsigned int irq, struct irq_chip *chip,
+ irq_flow_handler_t handle);
+extern void
set_irq_chip_and_handler_name(unsigned int irq, struct irq_chip *chip,
irq_flow_handler_t handle, const char *name);
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: Olaf Hering <olaf@aepfle.de>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: [patch] genirq: clean up irq-flow-type naming, fix
Date: Wed, 18 Oct 2006 10:16:59 +0200 [thread overview]
Message-ID: <20061018081659.GA5778@elte.hu> (raw)
In-Reply-To: <20061018080411.GA13340@aepfle.de>
* Olaf Hering <olaf@aepfle.de> wrote:
> There is no prototype anymore, but still many users.
>
> a460e745e8f9c75a0525ff94154a0629f9d3e05d is likely the culprit:
> [PATCH] genirq: clean up irq-flow-type naming
oops, that was unintended. The patch below should fix this.
Ingo
--------------->
Subject: genirq: clean up irq-flow-type naming, fix
From: Ingo Molnar <mingo@elte.hu>
re-add the set_irq_chip_and_handler() prototype, it's still widely used.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
include/linux/irq.h | 3 +++
1 file changed, 3 insertions(+)
Index: linux/include/linux/irq.h
===================================================================
--- linux.orig/include/linux/irq.h
+++ linux/include/linux/irq.h
@@ -322,6 +322,9 @@ extern struct irq_chip no_irq_chip;
extern struct irq_chip dummy_irq_chip;
extern void
+set_irq_chip_and_handler(unsigned int irq, struct irq_chip *chip,
+ irq_flow_handler_t handle);
+extern void
set_irq_chip_and_handler_name(unsigned int irq, struct irq_chip *chip,
irq_flow_handler_t handle, const char *name);
next prev parent reply other threads:[~2006-10-18 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 8:04 implicit declaration of function set_irq_chip_and_handler Olaf Hering
2006-10-18 8:16 ` Ingo Molnar [this message]
2006-10-18 8:16 ` [patch] genirq: clean up irq-flow-type naming, fix Ingo Molnar
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=20061018081659.GA5778@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olaf@aepfle.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.