From owner-freebsd-arch@FreeBSD.ORG Wed May 20 15:01:24 2009 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86325106566C; Wed, 20 May 2009 15:01:24 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 412418FC18; Wed, 20 May 2009 15:01:24 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id n4KExFk1056013; Wed, 20 May 2009 08:59:15 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 20 May 2009 08:59:24 -0600 (MDT) Message-Id: <20090520.085924.-1935226744.imp@bsdimp.com> To: jhb@freebsd.org From: "M. Warner Losh" In-Reply-To: <200905121020.18497.jhb@freebsd.org> References: <200905121020.18497.jhb@freebsd.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org Subject: Re: Remove d_thread_t for 8.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 May 2009 15:01:24 -0000 In message: <200905121020.18497.jhb@freebsd.org> John Baldwin writes: : In the same vein as purging BURN_BRIDGES stuff, is there any objection to : removing d_thread_t from 8.0? It is intended as a compat shim to reduce : diffs with 4.x. However, at this point drivers are not actively being merged : back to 4.x, so I think it is no longer necessary. It was also intended to allow easier sharing for folks that were using FreeBSD 4.x, 5.x, etc. I know that at least one user still has some 4.x deployments, but I suspect that they are otherwise off 4.x so it might not be a problem for them. It would be yet another thing to change when going from 7.x to 8.x for them... We certainly should remove it from the drivers in the tree for 8.0. Right now it is used in about a two dozen places. Warner