From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 1E03F4A6E for ; Mon, 17 Nov 2014 15:06:58 +0100 (CET) Received: from hmsreliant.think-freely.org ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1XqN76-0000cx-Ow; Mon, 17 Nov 2014 09:17:11 -0500 Date: Mon, 17 Nov 2014 09:17:08 -0500 From: Neil Horman To: Thomas Monjalon Message-ID: <20141117141708.GE17886@hmsreliant.think-freely.org> References: <1412045348-18543-1-git-send-email-jingjing.wu@intel.com> <9BB6961774997848B5B42BEC655768F8B04B34@SHSMSX104.ccr.corp.intel.com> <20141009112918.GA20940@hmsreliant.think-freely.org> <2311642.9a52mKMPYp@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2311642.9a52mKMPYp@xps13> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Score: -2.9 (--) X-Spam-Status: No Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] llib/ibrte_net: workaround to avoid macro conflict 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, 17 Nov 2014 14:06:58 -0000 On Mon, Nov 03, 2014 at 08:41:53AM +0100, Thomas Monjalon wrote: > 2014-10-09 07:29, Neil Horman: > > On Thu, Oct 09, 2014 at 05:20:31AM +0000, Wu, Jingjing wrote: > > > Hi, Neil > > > > > > To have rte_ip.h include netinet/in.h directly is also a choice. > > > > > > But netinet/in.h contains a lot of extra stuff, and these may be useless some DPDK applications, such as classification. > > > rte_ip.h provides a more simplify way for the IP protocol layer. > > > > > Not sure what the relevance there is. The definitions you want are > > standardized, theres no need for the dpdk to re-invent that wheel. Get them > > from the system include file. The fact that extra macros are available in > > netinet.h is neither relevant or true (as you can't really say for certain what > > an application will need). > > Neil, Matthew, > > I totally agree with your point of view. > Please, could you propose a patch to fix this issue? > Matthew, can you handle this please, I've got too much going on right now. Neil > Thanks > -- > Thomas >