From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 2F26C11F5 for ; Mon, 29 Sep 2014 23:27:40 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 647A780CD23; Mon, 29 Sep 2014 14:33:41 -0700 (PDT) Date: Mon, 29 Sep 2014 14:33:41 -0700 From: Matthew Hall To: Thomas Monjalon Message-ID: <20140929213341.GA589@mhcomputing.net> References: <1963310.3iizrFVzmj@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1963310.3iizrFVzmj@xps13> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] rc1 / call for review 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: Mon, 29 Sep 2014 21:27:40 -0000 On Mon, Sep 29, 2014 at 10:23:58PM +0200, Thomas Monjalon wrote: > - mbuf rework > - logs rework > - some eal cleanups Hi Thomas, I was curious, did we happen to know if any of these three changes affected the external API's much? It would help us get some idea what to test and where to look, since mbuf, logs, and eal are probably the three most popular parts of DPDK for us app hackers to interact with regularly. Thanks, Matthew.