From owner-freebsd-amd64@FreeBSD.ORG Sat Apr 29 14:20:12 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EB0116A400 for ; Sat, 29 Apr 2006 14:20:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AFEE43D45 for ; Sat, 29 Apr 2006 14:20:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 1A1DE20017E; Sat, 29 Apr 2006 16:20:09 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 5418B20017D; Sat, 29 Apr 2006 16:20:06 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7E9F8444F41; Sat, 29 Apr 2006 14:20:01 +0000 (UTC) Date: Sat, 29 Apr 2006 14:20:01 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: protagonist@gmx.net In-Reply-To: Message-ID: <20060429141928.T13011@maildrop.int.zabbadoz.net> References: <20060427120035.D7FA016A43B@hub.freebsd.org> <4450D0E8.4000403@uchicago.edu> <200604281646.46451.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-amd64@freebsd.org Subject: Re: nve(4) timeout fix X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Apr 2006 14:20:12 -0000 On Sat, 29 Apr 2006, Marcus Frings wrote: > * John Baldwin wrote: > > [nve fix] >>> Will it be added to the official release of 6.1 or CURRENT? > >> It's in current but is probably too late for 6.1. > > Okay, thanks for the information. Maybe I will switch to -CURRENT soon > if this fix doesn't get into 6.1. you could also apply the patch to 6 by hand and rebuild. That shouldn't be a problem. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT