From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 4CC56A0AC5 for ; Sat, 4 May 2019 23:32:14 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 3F9EA1F28; Sat, 4 May 2019 23:32:13 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id BFE67A49 for ; Sat, 4 May 2019 23:32:11 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4827A2013C; Sat, 4 May 2019 17:32:11 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sat, 04 May 2019 17:32:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=6mynV37kWP/D3tmQi4P4mG4Sc8KKfbC1Q0BOMmwoF2s=; b=ZGIYIu2BKW86 oHgmO34jUD1fLdsJsg6szSnqx4Lq/dZCd3iaP2qPiGMkTpakKAMfPlqwNKXPxR3+ Sos+mgIfux6/Cmx9XNBeSHV40ddJX4Otug4A8oLIsr24ILjj7WVqzY6b2ko5IV9m xhrDt5fApX8nnMex38XWhyVMisb5z1s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=6mynV37kWP/D3tmQi4P4mG4Sc8KKfbC1Q0BOMmwoF 2s=; b=oiIEUUuyfss7BoYE3SmgHddX3HS4KFZN3a0LoNxb7QnvdVjSgULwepjUT eXmbS/RlgLzSXIRLPZck0CD6CrCj+2hG83apA5qsGOQBLuauFJMulTCGpATBAwko FeQdMgbu60IVzyhQ4PocDYFhm/ZsW5+fYbKVwSy9V1gHPpkmNtK4kiLJYQ8xloYP z4VDTUR4w85ZWxAUyjpfFos0Jv4vwcoiaK19uG2SpjrLkD44KgidxWRVGuihMUpm 0mSGCMB6Br5kNQB9IPOvIrlWMjgNgXikD+E4i66jDIuibx1x77Y0JK6Urou6tbx6 b2QdX8yWR9NvbBXFuXX+YQO9+wkcQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrjeegucetufdoteggodetrfdotffvucfrrh hofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgenuceurghi lhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurh ephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcuofho nhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppeejje drudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghs sehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 046A7103CA; Sat, 4 May 2019 17:32:09 -0400 (EDT) From: Thomas Monjalon To: "Wang, Yipeng1" Cc: dev@dpdk.org, "Mcnamara, John" , "De Lara Guarch, Pablo" , "gentoorion@gmail.com" , "Burakov, Anatoly" Date: Sat, 04 May 2019 23:32:08 +0200 Message-ID: <3897516.Qjog6bcR5C@xps> In-Reply-To: References: <1556530816-423522-1-git-send-email-yipeng1.wang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] doc: fix rte_hash_hash comment for ambiguity X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190504213208.rVCGvZZ9FzdYINchlzzYVeA44LM1LFQkvNP8rLYDxiU@z> > > rte_hash_hash is multi-thread safe but not multi-process safe because of > > the use of function pointers. Previous document and comment says the other > > way around. This commit fixes the issue. > > Acked-by: John McNamara Applied, thanks