From owner-cvs-all@FreeBSD.ORG Thu Jul 31 13:18:55 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0CC9106566C; Thu, 31 Jul 2008 13:18:55 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id A0BE18FC14; Thu, 31 Jul 2008 13:18:55 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 96CEF46B94; Thu, 31 Jul 2008 09:18:54 -0400 (EDT) Date: Thu, 31 Jul 2008 14:18:54 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Jack F Vogel In-Reply-To: <200807302157.m6ULvGMT050324@repoman.freebsd.org> Message-ID: <20080731141655.G6383@fledge.watson.org> References: <200807302157.m6ULvGMT050324@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/dev/e1000 LICENSE README e1000_80003es2lan.c e1000_80003es2lan.h e1000_82540.c e1000_82541.c e1000_82541.h e1000_82542.c e1000_82543.c e1000_82543.h e1000_82571.c e1000_82571.h e1000_82575.c e1000_82575.h e1000_api.c e1000_api.h ... X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 31 Jul 2008 13:18:56 -0000 On Wed, 30 Jul 2008, Jack F Vogel wrote: > SVN rev 181027 on 2008-07-30 21:56:53Z by jfv > > Merge of the source for igb and em into dev/e1000, this > proved to be necessary to make the static drivers work > in EITHER/OR or BOTH configurations. Modules will still > build in sys/modules/igb or em as before. > > This also updates the igb driver for support for the 82576 > adapter, adds shared code fixes, and etc.... > > MFC after: ASAP These changes seem pretty big -- I hope your definition of "ASAP" differs from mine when it comes to the MFC, as I would take ASAP to mean "almost immediately". We generally require a minimum delay of three days for mall changes, and ideally several weeks for large ones, and this is almost always a good idea as it's interesting how the world becomes more complicated once there's widespread testing going on :-). Robert N M Watson Computer Laboratory University of Cambridge