Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753234AbZFENG0 (ORCPT ); Fri, 5 Jun 2009 09:06:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751419AbZFENGS (ORCPT ); Fri, 5 Jun 2009 09:06:18 -0400 Received: from aun.it.uu.se ([130.238.12.36]:46270 "EHLO aun.it.uu.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750999AbZFENGR (ORCPT ); Fri, 5 Jun 2009 09:06:17 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18985.4718.192222.884806@pilspetsen.it.uu.se> Date: Fri, 5 Jun 2009 14:41:18 +0200 From: Mikael Pettersson To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , "IDE" , "James Bottomley" , "Mikael Pettersson" , "Tejun Heo" Subject: Re: [Bug #13378] kernel/async.c broke pata_legacy.c In-Reply-To: References: <4to6E2myxvG.A.muC.aIbIKB@chimera> X-Mailer: VM 7.17 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1075 Lines: 26 Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.29. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=3D13378 > Subject : kernel/async.c broke pata_legacy.c > Submitter : Mikael Pettersson > Date : 2009-05-24 16:13 (7 days old) > References : http://marc.info/?l=3Dlinux-kernel&m=3D124318186507210&w=3D4 > Handled-By : James Bottomley > Patch : http://patchwork.kernel.org/patch/25699/ paga_legacy remains broken in 2.6.30-rc8, and I still have to apply the above-mentioned patch to make the affected machine boot. /Mikael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/