public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] #include <asm/irq.h> in interrupt.h
Date: Wed, 24 Aug 2005 12:08:57 +0200	[thread overview]
Message-ID: <20050824100857.GH5603@stusta.de> (raw)
In-Reply-To: <20050824092250.GA26726@infradead.org>

On Wed, Aug 24, 2005 at 10:22:50AM +0100, Christoph Hellwig wrote:
> On Wed, Aug 24, 2005 at 10:57:50AM +0200, Adrian Bunk wrote:
> > If #includ'ing interrupt.h should be enough for getting the prototype of 
> > e.g. enable_irq() on all architectures, we need this patch.
> 
> Per defintion you need to include <asm/irq.h> right now.  I'd like to change
> that to <linux/interrupt.h>, but not my including <asm/irq.h> there.
> We should just make the prototypes in <linux/interrupt.h> unconditional
> and get rid of the macro/inline tricks some architectures do, these calls
> aren't exactly fastpathes where that matters.

Looking at 2.6.13-rc6-mm2, the only architectures with own enable_irq() 
implementations are m68knommu and sparc.

On m68knommu, enable_irq() does nothing unless a hook is used that has 
no in-kernel users.

The 32bit sparc arch seems to be the only arch doing funky things.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-08-24 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24  8:57 [RFC: 2.6 patch] #include <asm/irq.h> in interrupt.h Adrian Bunk
2005-08-24  9:22 ` Christoph Hellwig
2005-08-24 10:08   ` Adrian Bunk [this message]
2005-08-24 10:44     ` Thomas Gleixner
2005-08-24 10:54       ` Adrian Bunk

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=20050824100857.GH5603@stusta.de \
    --to=bunk@stusta.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox