From owner-cvs-all@FreeBSD.ORG Thu May 1 18:06:26 2003 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFC6737B401; Thu, 1 May 2003 18:06:26 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77E9B43F93; Thu, 1 May 2003 18:06:25 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h4216OA7012606; Thu, 1 May 2003 19:06:24 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 01 May 2003 19:06:12 -0600 (MDT) Message-Id: <20030501.190612.124380423.imp@bsdimp.com> To: marcel@xcllnt.net From: "M. Warner Losh" In-Reply-To: <20030501193258.GB778@athlon.pn.xcllnt.net> References: <200304291911.h3TJB0E2076851@repoman.freebsd.org> <20030501193258.GB778@athlon.pn.xcllnt.net> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: cvs-src@FreeBSD.org cc: njl@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org cc: jhb@FreeBSD.org Subject: Re: cvs commit: src/sys/contrib/dev/acpica acconfig.h acenv.h acfreebsd.h acgcc.h acpi.h acpiosxf.h acpixf.h acutils.h dbcmds.c dbxface.c exfldio.c exsystem.c hwsleep.c psparse.c rscreate.c tbget.c utglobal.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 01:06:27 -0000 In message: <20030501193258.GB778@athlon.pn.xcllnt.net> Marcel Moolenaar writes: : The question: do people think we should try to get another ACPI : snapshot in (provided we have someone willing to do it) and thus : try to get it fixed the "official" way or are we ok with changing : contrib'd code in this case and revert to the vendor branch when : we do upgrade sometime after 5.1? We must have another snapshot with all the breakages that this import caused fixed. If Nate isn't willing to do it, I would be. In the long term it is in our best interest to get the issues resolved with the Intel code. Warner