[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110815100732.32695233@schatten.dmk.lab>
Date: Mon, 15 Aug 2011 10:07:32 +0200
From: Florian Mickler <florian@...kler.org>
To: Bruno Wolff III <bruno@...ff.to>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Maciej Rutecki <maciej.rutecki@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [Bug #37872] CPU lockup during boot
On Sun, 14 Aug 2011 21:39:57 -0500
Bruno Wolff III <bruno@...ff.to> wrote:
> On Sun, Aug 14, 2011 at 21:07:31 +0200,
> "Rafael J. Wysocki" <rjw@...k.pl> wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.39 and 3.0.
> >
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.39 and 3.0. Please verify if it still should
> > be listed and let the tracking team know (either way).
> >
> >
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=37872
> > Subject : CPU lockup during boot
> > Submitter : Bruno Wolff III <bruno@...ff.to>
> > Date : 2011-06-19 15:00 (57 days old)
> > Patch : https://bugzilla.kernel.org/show_bug.cgi?id=37872#c16
>
> I am not sure of the correct procedure, but the issue was fixed just
> before the 3.0 release and the ticket is currently in the RESOLVED state.
> Should I change it to closed?
Just paste the sha1 of the commit that fixed it into the bugzilla and
switch it to 'closed/code fix'.
Regards,
Flo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists