From: Greg KH <gregkh@suse.de>
To: Stefan Lippers-Hollmann <s.L-H@gmx.de>
Cc: linux-kernel@vger.kernel.org, sgruszka@redhat.com,
IvDoorn@gmail.com, linville@tuxdriver.com,
stable@vger.kernel.org
Subject: Re: Patch "rt2x00: handle spurious pci interrupts" has been added to the 3.1-stable tree
Date: Mon, 5 Dec 2011 13:01:27 -0800 [thread overview]
Message-ID: <20111205210127.GA26148@suse.de> (raw)
In-Reply-To: <201112030352.07030.s.L-H@gmx.de>
On Sat, Dec 03, 2011 at 03:52:05AM +0100, Stefan Lippers-Hollmann wrote:
> 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
> >
> > rt2x00: handle spurious pci 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:
> > rt2x00-handle-spurious-pci-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 23085d5796561625db4143a671f1de081f66ef08 Mon Sep 17 00:00:00 2001
> > From: Stanislaw Gruszka <sgruszka@redhat.com>
> > Date: Wed, 16 Nov 2011 13:58:42 +0100
> > Subject: rt2x00: handle spurious pci interrupts
> [...]
>
> This patch has been reverted again, due to
> http://patchwork.ozlabs.org/patch/127153/
> (this also applies to the 2.6.32 backport)
Thanks for letting me know, I've now reverted it from all stable trees
greg k-h
prev parent reply other threads:[~2011-12-05 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13228684632156@kroah.org>
2011-12-03 2:52 ` Stefan Lippers-Hollmann
2011-12-05 21:01 ` Greg KH [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=20111205210127.GA26148@suse.de \
--to=gregkh@suse.de \
--cc=IvDoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=s.L-H@gmx.de \
--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
Powered by JetHome