Date: Fri, 12 Jan 2018 20:04:24 +0100 From: Joel Dahl <joel@vnode.se> To: Maxim Sobolev <sobomax@freebsd.org> Cc: Pete Wright <pete@nomadlogic.org>, Marcin Wojtas <mw@semihalf.com>, freebsd-virtualization@freebsd.org, mk@semihalf.com Subject: Re: ena(4) is not in GENERIC, now default for some/all instances on AWS EC2 Message-ID: <20180112190423.GC39759@ymer.vnode.se> In-Reply-To: <CAH7qZfvxWxFd-qEiG4gfDBkD68xzDb=uNS4Nnptp0EjcWoE%2BRw@mail.gmail.com> References: <CAH7qZftm=J9N4TqEsTY9fdxw0RSAy-Y7ROJ8_4r21x7xHu8xqw@mail.gmail.com> <3b5baa95-e87e-a527-5917-777ba0d6bca4@nomadlogic.org> <CAH7qZfvxWxFd-qEiG4gfDBkD68xzDb=uNS4Nnptp0EjcWoE%2BRw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 11, 2018 at 10:14:55AM -0800, Maxim Sobolev wrote: > Well, that might work, but I am curious why do we have all other network 40 > or so drivers in the GENERIC but not this one. Considering significant > portion of FreeBSD systems deployed these days are going to be running on > the cloud this makes no sense to me. Is there some policy out there which > governs such decisions? Email current@ and ask if there are any objections before you add it to GENERIC? -- Joel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180112190423.GC39759>