From: Tony Lindgren <tony@atomide.com>
To: "Sørensen, Stefan" <Stefan.Sorensen@spectralink.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] ARM: OMAP2+: INTC: Acknowledge stuck active interrupts
Date: Thu, 13 Mar 2014 13:38:54 -0700 [thread overview]
Message-ID: <20140313203854.GA23432@atomide.com> (raw)
In-Reply-To: <20140307160600.GB3789@atomide.com>
* Tony Lindgren <tony@atomide.com> [140307 08:09]:
> * Sørensen, Stefan <Stefan.Sorensen@spectralink.com> [140307 04:44]:
> > On Thu, 2014-03-06 at 10:32 -0800, Tony Lindgren wrote:
> > > While playing with this, you may want to also do one more test and
> > > forward port these two patches adding checks for spurious interrupts:
> > >
> > > 6ccc4c0d ARM: OMAP3: Warn about spurious interrupts
> > > 846c29f1 ARM: OMAP3: Clean up spurious interrupt check logic
> > >
> > > Those got removed in commit:
> > >
> > > 667a11fa arm: omap2/3: Use generic irq chip
> > >
> > > If you get warnings with those checks about spurious interrupts there's
> > > also something else wrong or we're not understanding the problem fully.
> > > So it might be good to check before we apply this patch.
> >
> > No warnings with those patches. I also tried watching the spuriousirq
> > field in various places - nothing showed up.
>
> OK thanks for testing, that's good to hear.
Applying your patch into omap-for-v3.15/fixes with cc: stable.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-03-13 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 15:27 [PATCH] ARM: OMAP2+: INTC: Acknowledge stuck active interrupts Stefan Sørensen
2014-03-06 18:32 ` Tony Lindgren
2014-03-07 12:41 ` Sørensen, Stefan
2014-03-07 16:06 ` Tony Lindgren
2014-03-13 20:38 ` Tony Lindgren [this message]
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=20140313203854.GA23432@atomide.com \
--to=tony@atomide.com \
--cc=Stefan.Sorensen@spectralink.com \
--cc=linux-omap@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;
as well as URLs for NNTP newsgroup(s).