From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 48A985A65 for ; Wed, 8 Jul 2015 15:23:26 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP; 08 Jul 2015 06:21:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,431,1432623600"; d="scan'208";a="760584460" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.63]) by orsmga002.jf.intel.com with SMTP; 08 Jul 2015 06:21:44 -0700 Received: by (sSMTP sendmail emulation); Wed, 08 Jul 2015 14:21:42 +0025 Date: Wed, 8 Jul 2015 14:21:42 +0100 From: Bruce Richardson To: Pablo de Lara Message-ID: <20150708132142.GB5708@bricha3-MOBL3> References: <1436354854-30700-1-git-send-email-pablo.de.lara.guarch@intel.com> <1436354854-30700-2-git-send-email-pablo.de.lara.guarch@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1436354854-30700-2-git-send-email-pablo.de.lara.guarch@intel.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] hash: move rte_hash structure to C file and make it internal 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: Wed, 08 Jul 2015 13:23:26 -0000 On Wed, Jul 08, 2015 at 12:27:34PM +0100, Pablo de Lara wrote: > rte_hash structure should not be a public structure, > and therefore it should be moved to the C file and be declared > as internal. rte_hash_hash implementation is also moved > to the C file, as it uses the structure. > > This patch also removes part of a unit test that was checking > a field of the structure. > > Signed-off-by: Pablo de Lara Irrespective of whether or not we change the underlying hash table implementation this looks a good change to me. The rte_hash structure should not be used directly by any applications - the APIs all take pointers to the structure, so there should be no ABI breakage from this, I think. Therefore: Acked-by: Bruce Richardson