Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Thiemo Seufer <ths@networkno.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] Cleanup for plat_irq_dispatch functions
Date: Mon, 19 Mar 2007 01:46:05 +0000	[thread overview]
Message-ID: <20070319014604.GA5658@linux-mips.org> (raw)
In-Reply-To: <20070319001337.GB7744@networkno.de>

On Mon, Mar 19, 2007 at 12:13:37AM +0000, Thiemo Seufer wrote:

> the appended patch
>  - adds missing ST0_IM masks, which caused the logging of valid
>    interrupts as spurious
>  - stops pnx8550 to log every interrupt as spurious
>  - adds cause register masks for ip22/ip32, which caused handling
>    of masked interrupts
>  - removes some superfluous parentheses in the SNI interrupt code

Thanks for sorting this out.

Now, I think spurious_interrupt should be deleted, it delivers not too
much useful data and even the reasoning for adding it back in the dark
ages was fairly weak ...

  Ralf

  reply	other threads:[~2007-03-19  1:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19  0:13 [PATCH] Cleanup for plat_irq_dispatch functions Thiemo Seufer
2007-03-19  1:46 ` Ralf Baechle [this message]
2007-03-21 15:59   ` Maciej W. Rozycki

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=20070319014604.GA5658@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ths@networkno.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