From: Eric Sesterhenn / snakebyte <snakebyte@gmx.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [Patch 2/5] Cleanup LINUX_VERSION_CODE in drivers/net
Date: Mon, 19 Dec 2005 16:46:59 +0000 [thread overview]
Message-ID: <1135010819.9125.1.camel@alice> (raw)
In-Reply-To: <1134946431.7394.7.camel@alice>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
hi,
> can you give me some more information on this? Seems quite some
> irda drivers use the IRQ_NONE an friends macro.
Ah ok, seems it is already defined in include/linux/interrupt.h
so we dont need to define it in the driver. Here is a patch on
top of the other which simply removes it.
Signed-of-by: Eric Sesterhenn <snakebyte@gmx.de>
--- linux-2.6.15-rc5-git5/drivers/net/irda/vlsi_ir.h.orig 2005-12-19 17:44:31.000000000 +0100
+++ linux-2.6.15-rc5-git5/drivers/net/irda/vlsi_ir.h 2005-12-19 17:44:54.000000000 +0100
@@ -41,14 +41,6 @@
#define PCI_CLASS_SUBCLASS_MASK 0xffff
#endif
-/* in recent 2.5 interrupt handlers have non-void return value */
-#ifndef IRQ_RETVAL
-typedef void irqreturn_t;
-#define IRQ_NONE
-#define IRQ_HANDLED
-#define IRQ_RETVAL(x)
-#endif
-
/* some stuff need to check kernelversion. Not all 2.5 stuff was present
* in early 2.5.x - the test is merely to separate 2.4 from 2.5
*/
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-12-19 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 22:53 [KJ] [Patch 2/5] Cleanup LINUX_VERSION_CODE in drivers/net Eric Sesterhenn / snakebyte
2005-12-18 23:24 ` Adrian Bunk
2005-12-19 0:24 ` Eric Sesterhenn / snakebyte
2005-12-19 16:46 ` Eric Sesterhenn / snakebyte [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=1135010819.9125.1.camel@alice \
--to=snakebyte@gmx.de \
--cc=kernel-janitors@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 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.