From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 10 Jan 2012 15:23:35 +0100 (CET) From: Thomas Gleixner To: Linus Torvalds cc: Jonathan Nieder , Greg KH , linux-kernel@vger.kernel.org, stable@vger.kernel.org, akpm@linux-foundation.org, Alan Cox , Phil Miller Subject: Re: [27/27] clockevents: Set noop handler in clockevents_exchange_device() In-Reply-To: Message-ID: References: <20111207165611.GA19872@kroah.com> <20111207165602.672902223@clark.kroah.org> <20111229120956.GA31878@elie.Belkin> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-1423828635-1326205416=:3020" Sender: linux-kernel-owner@vger.kernel.org List-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-1423828635-1326205416=:3020 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Thu, 29 Dec 2011, Linus Torvalds wrote: > On Thu, Dec 29, 2011 at 4:09 AM, Jonathan Nieder wrote: > > > > This is basically the reverse of 7c1e768974 (clockevents: prevent > > clockevent event_handler ending up handler_noop, 2008-09-03). �The > > rationale for the latter still applies. > > Hmm. You seem to be right. Instead of applying this to stable, it > looks like we should revert it from mainline. > > > �People have been reporting > > the analagous patch to this one causing hangs on resume in 3.1.y and > > 3.2 release candidates: > > > > �- http://thread.gmane.org/gmane.linux.kernel/1233033 > > �- http://thread.gmane.org/gmane.linux.kernel/1233389 > > �- http://thread.gmane.org/gmane.linux.kernel/1233159 > > �- http://thread.gmane.org/gmane.linux.kernel/1227868/focus=1230877 > > > > So please consider reverting it for now. > > Thomas? It does seem to be broken and there do seem to be regression > reports about it. > > Should I revert it, or do you have alternative fixes? Hmm. I have no idea what broke. Will have a look. Thanks, tglx --8323328-1423828635-1326205416=:3020--