From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: rc1 / call for review Date: Tue, 30 Sep 2014 06:52:45 +0200 Message-ID: <1600627.I6ZYUK1NqR@xps13> References: <1963310.3iizrFVzmj@xps13> <20140929213341.GA589@mhcomputing.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Matthew Hall Return-path: In-Reply-To: <20140929213341.GA589-Hv3ogNYU3JfZZajBQzqCxQ@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2014-09-29 14:33, Matthew Hall: > On Mon, Sep 29, 2014 at 10:23:58PM +0200, Thomas Monjalon wrote: > > - mbuf rework > > - logs rework > > - some eal cleanups > > 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. You're right. During integration time, app hackers should be able to check the git history for these API changes. When it will be officially released, there will be some notes in the documentation to help porting applications. -- Thomas