public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver•com>
To: Michael Ellerman <michael@ellerman•id.au>
Cc: linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
	Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH] powerpc: warn on spurious irq events (but ratelimited)
Date: Mon, 21 Dec 2015 19:21:56 -0500	[thread overview]
Message-ID: <20151222002156.GB12458@windriver.com> (raw)
In-Reply-To: <1450743048.27983.1.camel@ellerman.id.au>

[Re: [PATCH] powerpc: warn on spurious irq events (but ratelimited)] On 22/12/2015 (Tue 11:10) Michael Ellerman wrote:

> On Mon, 2015-12-21 at 18:18 -0500, Paul Gortmaker wrote:
> > On Mon, Dec 7, 2015 at 8:38 PM, Paul Gortmaker
> > <paul.gortmaker@windriver•com> wrote:
> > > It might be worth warning on spurious IRQ events; they might
> > > point someone at a bogus DTS value or similar.
> > > 

[...]

> > 
> > If we did decide we cared about this patch, then no need for "irq" above, as
> > we already know it is equal to NO_IRQ.
> 
> I'm not convinced it's worth printing, we already have a counter in proc.
> 
> I think it's more likely to just lead to console spam.
> 
> But maybe I'm wrong and you can convince me otherwise :)

I'm not sure I can even convince myself, let alone others.   :)

Feel free to bin it.

Paul.
--

> 
> cheers
> 

      reply	other threads:[~2015-12-22  0:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  1:38 [PATCH] powerpc: warn on spurious irq events (but ratelimited) Paul Gortmaker
2015-12-21 23:18 ` Paul Gortmaker
2015-12-22  0:10   ` Michael Ellerman
2015-12-22  0:21     ` Paul Gortmaker [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=20151222002156.GB12458@windriver.com \
    --to=paul.gortmaker@windriver$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=michael@ellerman$(echo .)id.au \
    --cc=paulus@samba$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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