From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [Bug #13186] cpufreq timer teardown problem
Date: Sun, 26 Apr 2009 19:45:11 +0200
Message-ID: <200904261945.11690.rjw@sisk.pl>
References: <tur5OtdUm3E.A.r2B.7oE9JB@chimera> <egHshlwQQFE.A.X-B._oE9JB@chimera> <20090426162800.GB25774@Krystal>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S1755778AbZDZRpb@vger.kernel.org>
In-Reply-To: <20090426162800.GB25774@Krystal>
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <kernel-testers.vger.kernel.org>
Content-Type: Text/Plain; charset="us-ascii"
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Kernel Testers List <kernel-testers@vger.kernel.org>, stable@kernel.org

On Sunday 26 April 2009, Mathieu Desnoyers wrote:
> * Rafael J. Wysocki (rjw@sisk.pl) wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.28 and 2.6.29.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.28 and 2.6.29.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> 
> I've had no news that the patches I proposed has been considered for
> -stable. They fix the teardown problem here. So I guess it's better to
> wait for the patches to get into -stable before we close this bug ?

In fact the bug is closeable as soon as they are in the Linus' tree.  Are they
in it right now?

Thanks,
Rafael