From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: Linux 2.6.16-rc3 Date: Mon, 13 Feb 2006 00:12:40 -0800 Message-ID: <20060213001240.05e57d42.akpm@osdl.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org To: "Brown, Len" Cc: davem@davemloft.net, torvalds@osdl.org, linux-kernel@vger.kernel.org, axboe@suse.de, James.Bottomley@steeleye.com, greg@kroah.com, linux-acpi@vger.kernel.org, linux-usb-devel@lists.sourceforge.net, luming.yu@intel.com, lk@bencastricum.nl, sanjoy@mrao.cam.ac.uk, helgehaf@aitel.hist.no, fluido@fluido.as, gbruchhaeuser@gmx.de, Nicolas.Mailhot@LaPoste.net, perex@suse.cz, tiwai@suse.de, patrizio.bassi@gmail.com, bni.swe@gmail.com, arvidjaar@mail.ru, p_christ@hol.gr, ghrt@dial.kappa.ro, jinhong.hu@gmail.com, andrew.vasquez@qlogic.com, linux-scsi@vger.kernel.org, bcrl@kvack.org List-Id: linux-scsi@vger.kernel.org "Brown, Len" wrote: > > My point is that it that on the grand scale of bugs serious enough > to have an effect on the course of 2.6.16, this one doesn't qualify > unless the same issue is seen on other systems. I think we can assume that it will be seen there. 2.6.16 is going into distros and will have more exposure than 2.6.15, let alone 2.6.16-rcX.