Return-Path: <linux-kernel-owner+w=401wt.eu-S1757053AbZCDTMV@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757053AbZCDTMV (ORCPT <rfc822;w@1wt.eu>);
	Wed, 4 Mar 2009 14:12:21 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754434AbZCDTMD
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 4 Mar 2009 14:12:03 -0500
Received: from smtp1.linux-foundation.org ([140.211.169.13]:41809 "EHLO
	smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1752606AbZCDTMA (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 4 Mar 2009 14:12:00 -0500
Date: Wed, 4 Mar 2009 11:11:14 -0800
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: stefanr@s5r6.in-berlin.de, efault@gmx.de,
       James.Bottomley@HansenPartnership.com, jengelh@medozas.de,
       bharrosh@panasas.com, linux-scsi@vger.kernel.org,
       linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
       tglx@linutronix.de
Subject: Re: Large amount of scsi-sgpool objects
Message-Id: <20090304111114.aed7b225.akpm@linux-foundation.org>
In-Reply-To: <20090304112455.GB14593@elte.hu>
References: <20090303192212.GA20705@elte.hu>
	<1236115544.15993.22.camel@localhost.localdomain>
	<20090303214454.GA8288@elte.hu>
	<1236119990.24019.35.camel@localhost.localdomain>
	<20090303230323.GA21644@elte.hu>
	<49ADBE29.4040706@s5r6.in-berlin.de>
	<20090303234834.GA13389@elte.hu>
	<49AE221D.9010909@s5r6.in-berlin.de>
	<1236150752.6049.19.camel@marge.simson.net>
	<49AE32B5.9040603@s5r6.in-berlin.de>
	<20090304112455.GB14593@elte.hu>
X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.8.20; i486-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 891
Lines: 24

On Wed, 4 Mar 2009 12:24:55 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> FYI, we still have not tracked down the SCSI bug. Latest 
> tip:master is able to boot and work on the affected systems, 
> while the upstream kernel does not even boot because the fix (or 
> the revert, should the fix be deemed unwanted) is stuck in the 
> SCSI tree.

<wakes up>

There are fixes in the scsi tree?

Does the scsi tree fix all the regressions which you guys are seeing?

I must say that it seems to be awfully late in the cycle to have this
amount of breakage remaining in mainline when we know exactly which
patches need to be reverted to unbreak things.

--
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/