Date: Wed, 08 Nov 2006 19:43:23 +0100 From: Ivan Voras <ivoras@fer.hr> To: freebsd-stable@freebsd.org Subject: Re: em driver testing Message-ID: <eit8g8$o9e$1@sea.gmane.org> In-Reply-To: <455212F2.3030509@samsco.org> References: <68011C68-0962-4946-88E1-F36EE7C707DA@redstarling.com> <20061106221219.GA66676@hugo10.ka.punkt.de> <041201c701f9$37b2aed0$9603a8c0@claylaptop> <2a41acea0611061614n478efe77y82c0ebc2e1b01e19@mail.gmail.com> <d763ac660611062047n67058489jeca8d4c79e8c7490@mail.gmail.com> <2a41acea0611062242h42b1bde6w711e9a5039ed1a90@mail.gmail.com> <20061108144003.GA43734@zone3000.net><20061108154102.GA40238@icarus.home.lan> <45520532.3000603@samsco.org> <01c801c70358$3cac5200$b3db87d4@multiplay.co.uk> <455212F2.3030509@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Scott Long wrote: > My personally opinion is that the changes needed are too risky to rush > into 6.2 for all of the different drivers. For the vast majority of > people, what is in 6.2 works quite well, and there is no need to > introduce new bugs. We are pushing forward with if_em because the > problems there are pretty widespread, and Intel is providing direct > engineering and QA input. Thus, risk is reduced. >From a purely user's point of view, it would be nice if the problems were clearly mentioned in errata together with links to the newest patches or some other kind of pointer to the ongoing work so people know where to look if these bugs hit them.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eit8g8$o9e$1>