From: Austin Schuh <austin@peloton-tech.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
Wolfgang Grandegger <wg@grandegger.com>,
Pavel Pisa <pisa@cmp.felk.cvut.cz>,
Marc Kleine-Budde <mkl@pengutronix.de>,
linux-can@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] genirq: Sanitize spurious interrupt detection of threaded irqs
Date: Mon, 28 Apr 2014 13:20:58 -0700 [thread overview]
Message-ID: <CANGgnMavy-W8UXosgBrLkSLU=rYvU36OJCE0qgZQ4N6iSdN82A@mail.gmail.com> (raw)
In-Reply-To: <CANGgnMahGUooVsRLuNd0UyA6bZk1=a_zL+Uqi7AGHrJn1EMxcg@mail.gmail.com>
On Mon, Apr 7, 2014 at 1:08 PM, Austin Schuh <austin@peloton-tech.com> wrote:
> On Mon, Apr 7, 2014 at 1:07 PM, Thomas Gleixner <tglx@linutronix.de> wrote:
>> On Mon, 7 Apr 2014, Austin Schuh wrote:
>>> You originally sent the patch out. I could send your patch out back
>>> to you, but that feels a bit weird ;)
>>
>> Wheee. Let me dig in my archives ....
>
> https://lkml.org/lkml/2013/3/7/222 in case that helps.
Did you find the patch? I didn't see anything go by (but I'm not on
the main mailing list and didn't find anything with a quick Google
search.) It would be nice to not need to run a custom kernel to keep
my machine running. I have what is probably a year split between 2
machines of runtime with the patch applied, and I haven't seen any
problems with it.
Austin
next prev parent reply other threads:[~2014-04-28 20:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANGgnMbszHzYe9pF2C6wag4MY_PfBG2qrMCC=rMmQnb-jyXXXw@mail.gmail.com>
[not found] ` <52CAB05F.4010303@hartkopp.net>
2014-04-07 18:38 ` [PATCH] genirq: Sanitize spurious interrupt detection of threaded irqs Austin Schuh
2014-04-07 18:41 ` Thomas Gleixner
2014-04-07 20:05 ` Austin Schuh
2014-04-07 20:07 ` Thomas Gleixner
2014-04-07 20:08 ` Austin Schuh
2014-04-28 20:20 ` Austin Schuh [this message]
2014-04-28 20:44 ` Thomas Gleixner
2013-03-07 13:53 Thomas Gleixner
2013-03-08 14:47 ` Till Straumann
2013-03-08 16:12 ` Thomas Gleixner
2013-03-08 17:19 ` Till Straumann
2013-03-08 19:41 ` Thomas Gleixner
2013-03-12 13:22 ` Till Straumann
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='CANGgnMavy-W8UXosgBrLkSLU=rYvU36OJCE0qgZQ4N6iSdN82A@mail.gmail.com' \
--to=austin@peloton-tech.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=pisa@cmp.felk.cvut.cz \
--cc=socketcan@hartkopp.net \
--cc=tglx@linutronix.de \
--cc=wg@grandegger.com \
/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).