public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andrey Panin" <pazke@orbita1.ru>
To: Miles Bader <miles@gnu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] irq handling code consolidation (common part)
Date: Tue, 24 Dec 2002 09:28:35 +0300	[thread overview]
Message-ID: <20021224062835.GC1222@pazke> (raw)
In-Reply-To: <buok7i0szhf.fsf@mcspd15.ucom.lsi.nec.co.jp>

On Tue, Dec 24, 2002 at 03:27:40PM +0900, Miles Bader wrote:
> "Andrey Panin" <pazke@orbita1.ru> writes:
> > this patch moves some common parts of irq handling code to one place.
> > Arch specific patches will follow. Patch for i386 is tested and performed 
> > well, but other arch specific patched are not. Please take a look.
> 
> Hmm, well it looks like it will work perfectly with the v850 (which
> makes sense as it's mostly a copy of the i386 code).
I have a patch for v850 already, I'll send it soon.
 
> What about request_irq/setup_irq?  The majority of architectures use
> exactly the same code as i386 for these; a few do not, so perhaps this
> is a case where a HAVE_ARCH_... define could be used.
> 
> [setup_irq even has this comment:
> 
>    /* this was setup_x86_irq but it seems pretty generic */
>    int setup_irq(unsigned int irq, struct irqaction * new)
> ]
It will be the next part of work. I'm changing my job now and
lack of time limits my perfomance :(

> -Miles
> -- 
> Come now, if we were really planning to harm you, would we be waiting here, 
>  beside the path, in the very darkest part of the forest?

-- 
Andrey Panin		| Embedded systems software developer
pazke@orbita1.ru	| PGP key: wwwkeys.pgp.net

  reply	other threads:[~2002-12-24  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-24  6:03 [RFC] irq handling code consolidation (common part) Andrey Panin
2002-12-24  6:21 ` Miles Bader
2002-12-24  6:27 ` Miles Bader
2002-12-24  6:28   ` Andrey Panin [this message]
2003-01-02 18:30 ` David Mosberger
2003-01-04  5:03   ` Andrey Panin
2003-01-04  6:12     ` David Mosberger

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=20021224062835.GC1222@pazke \
    --to=pazke@orbita1.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles@gnu.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