From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by dpdk.org (Postfix) with ESMTP id C7361CF9 for ; Sun, 18 Jan 2015 01:30:52 +0100 (CET) Received: by mail-qa0-f47.google.com with SMTP id n8so20049566qaq.6 for ; Sat, 17 Jan 2015 16:30:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8E/fzTjr3Xl4+VyLe1CZB+lkmv7R20I8+JpbtWczg+Q=; b=Lsa0cYreCuBl8A882kyZFSTgFV45XpKxWyYySAVAFArbO5dmJz61Eh6YD6vtx3nadJ DDDaRa1rAN7opM3c/BTSo30nhR046sHz7IlSCB01Eqev/6LVlPC5UBCNvkfxqKK478aI 6Eq8Xuq2fco94kyQi/Lq+ThkOEWKKXT9WiY+VAz0IOTQGsghXbC9h7/B+7zRKcVjGyKk +gP7WOYDwdZMIO/OFzCuXdYVCdpKwax415t5QiuSej0IwNusyFbj9XXfB+U0jarqQJvP eeP5MQJsTfM+mA1Grn/Y+4A76MErWtbWejr5zI4G8eeDpub/2lxc2T0wMknMSmmhs+6k M/6A== X-Gm-Message-State: ALoCoQnU5THI/oZprxrS8blG2MZpz2OTyCH0y/P2+s/gtKwEGipCXuSXfmQe6U8u7n+2W903uqmW MIME-Version: 1.0 X-Received: by 10.140.88.48 with SMTP id s45mr35051688qgd.28.1421541051922; Sat, 17 Jan 2015 16:30:51 -0800 (PST) Received: by 10.140.16.19 with HTTP; Sat, 17 Jan 2015 16:30:51 -0800 (PST) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54CA4BCC@IRSMSX102.ger.corp.intel.com> References: <20150114122352.63ef79eb@urahara> <1717148.0lUn7GOqmp@xps13> <20150115130616.GA22455@hmsreliant.think-freely.org> <12253538.YOLaLVcskf@xps13> <20150115185112.GC22455@hmsreliant.think-freely.org> <26FA93C7ED1EAA44AB77D62FBE1D27BA54C9978E@IRSMSX102.ger.corp.intel.com> <20150116165119.GC27496@hmsreliant.think-freely.org> <26FA93C7ED1EAA44AB77D62FBE1D27BA54CA4BCC@IRSMSX102.ger.corp.intel.com> Date: Sat, 17 Jan 2015 16:30:51 -0800 Message-ID: From: Stephen Hemminger To: "O'driscoll, Tim" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Why nothing since 1.8.0? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2015 00:30:53 -0000 I am all for having multiple staging trees that get MERGED into one upstream tree. Let me make it simple, no out of tree drivers. I am not supporting, maintaining or submitting drivers that are not in the mainline DPDK product. If you want me to submit drivers, then they should go into the mainstream. Developers: Want to be able to make changes to core infrastructure during merge window and fix all the related drivers. For many devices, developer wants to be able to submit a driver and have it fixed by others in the main tree. Vendors: Want to be able to extend, change, and enhance the existing DPDK tree and then build an application with that. It is a increase in technical overhead to merge in drivers from multiple sources.