From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: gregkh@suse.de
Cc: linux-kernel@vger.kernel.org, sgruszka@redhat.com,
IvDoorn@gmail.com, linville@tuxdriver.com,
stable@vger.kernel.org
Subject: Re: Patch "rt2800pci: handle spurious interrupts" has been added to the 3.1-stable tree
Date: Sat, 3 Dec 2011 03:50:14 +0100 [thread overview]
Message-ID: <201112030350.16436.s.L-H@gmx.de> (raw)
In-Reply-To: <13228684624108@kroah.org>
Hi
On Saturday 03 December 2011, gregkh@suse.de wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> rt2800pci: handle spurious interrupts
>
> to the 3.1-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> rt2800pci-handle-spurious-interrupts.patch
> and it can be found in the queue-3.1 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
> From 4ba7d9997869d25bd223dea7536fc1ce9fab3b3b Mon Sep 17 00:00:00 2001
> From: Stanislaw Gruszka <sgruszka@redhat.com>
> Date: Wed, 16 Nov 2011 11:09:17 +0100
> Subject: rt2800pci: handle spurious interrupts
[...]
This patch has been reverted again, due to
http://patchwork.ozlabs.org/patch/127153/
commit 82e5fc2a34fa9ffea38f00c4066b7e600a0ca5e6
Author: John W. Linville <linville@tuxdriver.com>
Date: Tue Nov 22 16:38:19 2011 -0500
Revert "rt2800pci: handle spurious interrupts"
This reverts commit 4ba7d9997869d25bd223dea7536fc1ce9fab3b3b.
The original patch was a misguided attempt to improve performance on
some hardware that is apparently prone to spurious interrupt generation.
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Regards
Stefan Lippers-Hollmann
next parent reply other threads:[~2011-12-03 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13228684624108@kroah.org>
2011-12-03 2:50 ` Stefan Lippers-Hollmann [this message]
2011-12-05 21:02 ` Greg KH
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=201112030350.16436.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=IvDoorn@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.com \
--cc=stable@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
all inboxes | Powered by JetHome®