From: Thomas Gleixner <tglx@linutronix.de>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: AVR32 architecture patch against Linux 2.6.18-rc1 available
Date: Thu, 06 Jul 2006 14:10:07 +0200 [thread overview]
Message-ID: <1152187808.24611.142.camel@localhost.localdomain> (raw)
In-Reply-To: <20060706135027.140c6f8c@cad-250-152.norway.atmel.com>
On Thu, 2006-07-06 at 13:50 +0200, Haavard Skinnemoen wrote:
> On Thu, 06 Jul 2006 13:30:25 +0200
> Thomas Gleixner <tglx@linutronix.de> wrote:
>
> > On Thu, 2006-07-06 at 12:03 +0200, Haavard Skinnemoen wrote:
> > > > Looks pretty sane from a quick scan.
> > > >
> > > > - request_irq() can use GFP_KERNEL?
> > >
> > > Probably, but the genirq implementation also uses GFP_ATOMIC.
> >
> > Is there a good reason, why AVR32 needs its own interrupt handling
> > implementation ?
>
> No, not really. At least not after the genirq stuff went in. I used to
> be a bit concerned about the generic irq code being too heavyweight,
> but I think handle_simple_irq() might be just what we need for
> chip-internal interrupt handling.
>
> > >From a short glance there's nothing which can not be handled by the
> > generic code. Also there are a couple of things missing -e.g.
> > recursive enable/disable_irq() handling.
>
> You're probably right. I'll see if I can get it converted to genirq
> one of the next days.
Good. If there are any questions or things you find missing, don't
hesitate to ask.
tglx
next prev parent reply other threads:[~2006-07-06 12:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 8:52 AVR32 architecture patch against Linux 2.6.18-rc1 available Haavard Skinnemoen
2006-07-06 9:19 ` Andrew Morton
2006-07-06 9:51 ` Russell King
2006-07-06 9:58 ` Arjan van de Ven
2006-07-06 10:43 ` Haavard Skinnemoen
2006-07-06 15:17 ` Russell King
2006-07-06 10:03 ` Haavard Skinnemoen
2006-07-06 10:14 ` Andrew Morton
2006-07-06 13:57 ` Haavard Skinnemoen
2006-07-10 9:03 ` Haavard Skinnemoen
2006-07-10 9:31 ` Andrew Morton
2006-07-10 9:37 ` Andrew Morton
2006-07-10 11:04 ` Haavard Skinnemoen
2006-07-10 9:57 ` David Woodhouse
2006-07-10 11:25 ` Haavard Skinnemoen
2006-07-06 11:30 ` Thomas Gleixner
2006-07-06 11:50 ` Haavard Skinnemoen
2006-07-06 12:10 ` Thomas Gleixner [this message]
2006-07-06 11:58 ` David Woodhouse
2006-07-06 14:13 ` Haavard Skinnemoen
2006-07-06 14:34 ` David Woodhouse
2006-07-06 18:48 ` Haavard Skinnemoen
2006-07-06 23:17 ` David Woodhouse
2006-07-07 10:39 ` Haavard Skinnemoen
2006-07-07 10:44 ` Arjan van de Ven
2006-07-07 8:08 ` Nick Piggin
2006-07-07 8:18 ` Nick Piggin
2006-07-07 16:36 ` Haavard Skinnemoen
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=1152187808.24611.142.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@osdl.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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