From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by dpdk.org (Postfix) with ESMTP id 471BA5A71 for ; Fri, 8 May 2015 12:02:49 +0200 (CEST) Received: by wgyo15 with SMTP id o15so67852396wgy.2 for ; Fri, 08 May 2015 03:02:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=3XlmolXnajot9DCsPGNgAryfvulkY0SbszUwxylrZC8=; b=Drm2bZ1Je1oRD5T0i2Qnd6ei2RvCavzhgpn9rA/rbyAqpo2OtefP+aPFMVqzjfC0wr A5etsfaFN1izkbD793ez56RraVnFkgcCU1h9hUfiiAsrF2Y7Aru6qpJ80ueR29MqALtz BT3qJssd+W7VRtD4oTHH1bNaWgVex99D3lufoGjKKU1YLYVWNyEz+S+fdkjtNtZTlGUt nvlS0DSA6bXBK0Ivn/Liq7vrf0V9pjKk/fo80le0YxYAfR9AistTezNbnzmWLG77zRtc ljugZZTtSsFHpPCF2UAwekhjSnPWoNXdK98m/tdBnVGpQN0XldJag9/hcWmVJTQzIQdq rEvA== MIME-Version: 1.0 X-Received: by 10.180.104.225 with SMTP id gh1mr4642180wib.65.1431079369162; Fri, 08 May 2015 03:02:49 -0700 (PDT) Sender: lukego@gmail.com Received: by 10.27.134.198 with HTTP; Fri, 8 May 2015 03:02:48 -0700 (PDT) In-Reply-To: <20150508094233.GC7376@bricha3-MOBL3> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D29B55@IRSMSX102.ger.corp.intel.com> <554B85D5.6010808@cloudius-systems.com> <554B8D48.7010900@cloudius-systems.com> <20150508090645.GA7376@bricha3-MOBL3> <20150508094233.GC7376@bricha3-MOBL3> Date: Fri, 8 May 2015 12:02:48 +0200 X-Google-Sender-Auth: MhZsr5p7BKLch1IpqMv9b6Ya6sc Message-ID: From: Luke Gorrie To: Bruce Richardson Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Beyond DPDK 2.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: Fri, 08 May 2015 10:02:49 -0000 On 8 May 2015 at 11:42, Bruce Richardson wrote: > The code in those directories is "common" code that is maintained by Intel > - > which is why you see repeated comments about not modifying it for DPDK. It > is > just contained in it's own subfolder in each DPDK driver for easier > updating > off the internal Intel baseline. > Thanks for pointing this out to me, Bruce. Food for thought. Cheers, -Luke