Date: Wed, 20 Feb 2013 11:05:10 -0800 From: Juli Mallett <jmallett@FreeBSD.org> To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= <des@des.no> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Jack Vogel <jfvogel@gmail.com> Subject: Re: svn commit: r247035 - head/sys/dev/ixgbe Message-ID: <CACVs6=_aLDsNyUzihknkBjSeZsm920_Qga4bx-XtY9ho7WneFg@mail.gmail.com> In-Reply-To: <86ip5mbyoj.fsf@ds4.des.no> References: <201302201259.r1KCxMUZ076597@svn.freebsd.org> <CAFOYbckumY2SKA%2BEMmTad8usQXwRRrw5bCJ3erQFR9ZK1uNVzg@mail.gmail.com> <86ip5mbyoj.fsf@ds4.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 20, 2013 at 10:57 AM, Dag-Erling Sm=C3=B8rgrav <des@des.no> wro= te: > Jack Vogel <jfvogel@gmail.com> writes: >> OK, this change must be backed out. This was not run past me, and this >> is a shared code file, that means its code that we license in both >> GPL, BSD, and closed source licensing, and thus we CANNOT accept >> changes without special handling. Further, I do not author this code, >> its done by another team internally, and I simply accept it as a >> component. > > I think you're confused. I did not commit this to Intel's code > repository. I committed it to FreeBSD's code repository as a precursor > to a slightly more extensive patch which I intend to commit once I've > tested it more thoroughly. Please don't. Many others have accepted/respected Jack's maintainership by letting him keep control of the in-tree driver as much as is possible, particularly outside of ixgbe.c. I would love to have committed my code to handle 1G SFPs quite some time ago, but it makes at least a little sense to me that Jack handles the merges and testing and whatnot and doesn't need the additional work of maintaining FreeBSD additions he can't test. In general, the benefit of having the Intel drivers updated regularly by someone who has done extensive testing and who has the backing of Intel has outweighed the cost of deferring to Intel and Jack about what can go into the drivers. If your changes are so compelling, I would have expected them to have appeared at least on a major public mailing list, rather than committed at a whim to a driver which has a clear and obvious maintainer. If we really do have a lot of wonderful changes that are stalled by Jack's maintainership, provide a second driver in-tree and maintain it, which has all the go-faster/better/stronger stripes. It's not just Jack that unexpected changes to these critical drivers make things harder for. There's Luigi, Ryan Stone, John Baldwin, myself and others, who maintain extensions to the Intel drivers in-tree and/or privately. Thanks, Juli.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACVs6=_aLDsNyUzihknkBjSeZsm920_Qga4bx-XtY9ho7WneFg>