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 EDF4E5690 for ; Mon, 16 Mar 2015 16:45:57 +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 1YXXDG-0007O1-Lm; Mon, 16 Mar 2015 11:45:56 -0400 Date: Mon, 16 Mar 2015 11:45:53 -0400 From: Neil Horman To: "Mcnamara, John" Message-ID: <20150316154553.GD16238@hmsreliant.think-freely.org> References: <1426510564-19164-1-git-send-email-john.mcnamara@intel.com> <20150316131916.GC16238@hmsreliant.think-freely.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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] eal: fix Wbad-function-cast warning 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, 16 Mar 2015 15:45:58 -0000 On Mon, Mar 16, 2015 at 03:04:45PM +0000, Mcnamara, John wrote: > > -----Original Message----- > > From: Neil Horman [mailto:nhorman@tuxdriver.com] > > Sent: Monday, March 16, 2015 1:19 PM > > To: Mcnamara, John > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH] eal: fix Wbad-function-cast warning > > > > > > This looks reasonable, but it rather begs the question as to why we need > > rte_align_floor_int in the first place. Theres only one other call site, > > and it looks like it could use RTE_PTR_ALIGN_FLOOR just as easily. What > > about fixing up the second call site and removing the function to save > > some space? > > Hi Neil, > > Seems like a good idea. I'll submit a v2. > > Does rte_align_floor_int() need to be deprecated in some way or is it okay to just remove it? > > John > After the 2.0 release you should put a note in the api document, yes, but right now its not required. Though if you wanted to, I wouldn't stop you :) Neil