Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265385AbUADLgJ (ORCPT ); Sun, 4 Jan 2004 06:36:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265400AbUADLgJ (ORCPT ); Sun, 4 Jan 2004 06:36:09 -0500 Received: from mta05-svc.ntlworld.com ([62.253.162.45]:65469 "EHLO mta05-svc.ntlworld.com") by vger.kernel.org with ESMTP id S265385AbUADLgI (ORCPT ); Sun, 4 Jan 2004 06:36:08 -0500 Date: Sun, 4 Jan 2004 11:36:30 +0000 From: DaMouse Networks To: linux-kernel@vger.kernel.org Subject: Re: 2.6.1-rc1-mjb1 Message-Id: <20040104113630.78a94dcd@EozVul.WORKGROUP> Organization: DaMouse Networks X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i686-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 X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 445 Lines: 8 I'm just wondering how the HT schedular merge is coming? I'm interesting in getting a better/new one for some testing so I wondered how it was coming along with it being ported to 2.6.1-rc1. -DaMouse - 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/