From: Andrew Morton <akpm@osdl.org>
To: tglx@linutronix.de
Cc: bunk@stusta.de, linux-kernel@vger.kernel.org, mingo@elte.hu,
rmk@arm.linux.org.uk
Subject: Re: 2.6.17-mm3: arm: *_irq_wake compile error
Date: Wed, 28 Jun 2006 00:12:08 -0700 [thread overview]
Message-ID: <20060628001208.2b034afd.akpm@osdl.org> (raw)
In-Reply-To: <1151478544.25491.485.camel@localhost.localdomain>
On Wed, 28 Jun 2006 09:09:04 +0200
Thomas Gleixner <tglx@linutronix.de> wrote:
> On Wed, 2006-06-28 at 00:40 +0200, Adrian Bunk wrote:
> > genirq-add-irq-wake-power-management-support.patch causes the following
> > compile error on arm:
> >
> > <-- snip -->
> >
> > ...
> > CC init/main.o
> > In file included from include/linux/rtc.h:102,
> > from include/linux/efi.h:19,
> > from init/main.c:47:
> > include/linux/interrupt.h:108: error: conflicting types for 'enable_irq_wake'
> > include/asm/irq.h:47: error: previous declaration of 'enable_irq_wake' was here
> > include/linux/interrupt.h:113: error: conflicting types for 'disable_irq_wake'
> > include/asm/irq.h:46: error: previous declaration of 'disable_irq_wake' was here
> > make[1]: *** [init/main.o] Error 1
>
> Thats a mismerge with LOCKDEP
>
> This section was originally inside #ifdef CONFIG_GENERIC_HARDIRQS
>
> /* IRQ wakeup (PM) control: */
> extern int set_irq_wake(unsigned int irq, unsigned int on);
>
> static inline int enable_irq_wake(unsigned int irq)
> {
> return set_irq_wake(irq, 1);
> }
>
> static inline int disable_irq_wake(unsigned int irq)
> {
> return set_irq_wake(irq, 0);
> }
>
> The patch is:
>
> lockdep-add-disable-enable_irq_lockdep-api.patch
>
OK, so I moved the above lines inside #ifdef CONFIG_GENERIC_HARDIRQS (diff
did a strange-looking thing with it):
diff -puN include/linux/interrupt.h~lockdep-add-disable-enable_irq_lockdep-api-fix include/linux/interrupt.h
--- a/include/linux/interrupt.h~lockdep-add-disable-enable_irq_lockdep-api-fix
+++ a/include/linux/interrupt.h
@@ -71,17 +71,6 @@ static inline void enable_irq_lockdep(un
#endif
enable_irq(irq);
}
-#else /* !CONFIG_GENERIC_HARDIRQS */
-/*
- * NOTE: non-genirq architectures, if they want to support the lock
- * validator need to define the methods below in their asm/irq.h
- * files, under an #ifdef CONFIG_LOCKDEP section.
- */
-# ifndef CONFIG_LOCKDEP
-# define disable_irq_nosync_lockdep(irq) disable_irq_nosync(irq)
-# define disable_irq_lockdep(irq) disable_irq(irq)
-# define enable_irq_lockdep(irq) enable_irq(irq)
-# endif
/* IRQ wakeup (PM) control: */
extern int set_irq_wake(unsigned int irq, unsigned int on);
@@ -96,6 +85,18 @@ static inline int disable_irq_wake(unsig
return set_irq_wake(irq, 0);
}
+#else /* !CONFIG_GENERIC_HARDIRQS */
+/*
+ * NOTE: non-genirq architectures, if they want to support the lock
+ * validator need to define the methods below in their asm/irq.h
+ * files, under an #ifdef CONFIG_LOCKDEP section.
+ */
+# ifndef CONFIG_LOCKDEP
+# define disable_irq_nosync_lockdep(irq) disable_irq_nosync(irq)
+# define disable_irq_lockdep(irq) disable_irq(irq)
+# define enable_irq_lockdep(irq) enable_irq(irq)
+# endif
+
#endif /* CONFIG_GENERIC_HARDIRQS */
#ifndef __ARCH_SET_SOFTIRQ_PENDING
_
next prev parent reply other threads:[~2006-06-28 7:15 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 8:52 2.6.17-mm3 Andrew Morton
2006-06-27 9:14 ` 2.6.17-mm3: no help text for READAHEAD_ALLOW_OVERHEADS Adrian Bunk
[not found] ` <20060627134337.GA6117@mail.ustc.edu.cn>
2006-06-27 13:43 ` Wu Fengguang
2006-06-27 14:40 ` Adrian Bunk
[not found] ` <20060627155227.GA6014@mail.ustc.edu.cn>
2006-06-27 15:52 ` Wu Fengguang
2006-06-27 17:46 ` Randy.Dunlap
2006-06-27 17:55 ` Adrian Bunk
2006-06-27 9:28 ` [patch] irq: fix arch/i386/kernel/irq.c gcc warning Ingo Molnar
2006-06-27 11:06 ` Björn Steinbrink
2006-06-27 11:14 ` x86_64-mm-ieee1394-early.patch (was Re: 2.6.17-mm3) Stefan Richter
2006-06-27 11:17 ` 2.6.17-mm3 Reuben Farrelly
2006-06-27 11:48 ` 2.6.17-mm3 Reuben Farrelly
2006-06-27 14:12 ` 2.6.17-mm3 Michal Piotrowski
2006-06-27 21:38 ` 2.6.17-mm3 Steve Fox
2006-06-27 23:12 ` 2.6.17-mm3 Martin Bligh
2006-06-27 22:40 ` 2.6.17-mm3: arm: *_irq_wake compile error Adrian Bunk
2006-06-28 7:09 ` Thomas Gleixner
2006-06-28 7:12 ` Andrew Morton [this message]
2006-06-28 7:20 ` Thomas Gleixner
2006-06-28 8:13 ` Ingo Molnar
2006-06-28 8:30 ` [patch] genirq: rename desc->handler to desc->chip, sparc64 fix Ingo Molnar
2006-06-28 8:39 ` David Miller
2006-06-28 8:48 ` Andrew Morton
2006-06-28 8:47 ` Ingo Molnar
2006-06-28 9:24 ` David Miller
2006-06-29 4:58 ` Paul Mackerras
2006-06-29 6:42 ` Ingo Molnar
2006-06-28 12:03 ` 2.6.17-mm3 - mutex warning in usbhid, battery problem, and slab corruption Rafael J. Wysocki
2006-06-28 12:09 ` Andrew Morton
2006-06-28 14:14 ` 2.6.17-mm3 Cedric Le Goater
2006-06-28 16:54 ` [-mm patch] make drivers/scsi/aic7xxx/aic79xx_core.:ahd_set_tags() static Adrian Bunk
2006-06-28 16:54 ` [-mm patch] kernel/rcutorture.c: make code static Adrian Bunk
2006-06-28 17:13 ` Paul E. McKenney
2006-06-28 17:17 ` Adrian Bunk
2006-06-28 17:49 ` Paul E. McKenney
2006-06-28 20:18 ` Paul E. McKenney
2006-06-28 16:55 ` [-mm patch] kernel/lockdep.c: possible cleanups Adrian Bunk
2006-06-29 13:49 ` Ingo Molnar
2006-06-28 16:55 ` [-mm patch] fs/ecryptfs/: " Adrian Bunk
2006-06-28 18:40 ` Michael Halcrow
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=20060628001208.2b034afd.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rmk@arm.linux.org.uk \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox