From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id AD0671B2BD for ; Wed, 14 Feb 2018 11:59:24 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 46F0B208A1; Wed, 14 Feb 2018 05:59:24 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 14 Feb 2018 05:59:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=zjeQ0PNuMH0yl4kqsKVMjF1MFS nWw4cjqYNNQMaCKfo=; b=M7HUNKIS1w3rTR8NaZKSTz6se1an0S5+m5oQUJKvhm R8Twhq0dgNb6MG9HBRk9oGNfpfaUVEe9Fsbv6LUdfQ/vswy6v1TFJMlApDyCKxL+ u4RYgEqeTXj3JVD3qnjKoRwDF9VxOML5oNNP0gvRlmO9YKjIdlJBWk3QmchgFUuR Y= 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-sender:x-me-sender:x-sasl-enc; s=fm2; bh=zjeQ0P NuMH0yl4kqsKVMjF1MFSnWw4cjqYNNQMaCKfo=; b=P8z9vCEdvUeSYMKEO/KMgy psCd3Hbd/o9PUOkcYYyo3MlQK7YcRsE6KMYyl5LW1haZPUcMkLNbVMFDg3z63SVh fNYnMBi3ICcrMwbBIluGThlY05+dkzwHybqD/2I85HBsOqFYSQIGbGjriKPkRhdG nLL0ycTVx8IJGRNJWfb1KSQMoAurP48vbaV8XeJ7VUdQ/u3yeX/zIjMZS+He2yBl 56g8mG8N7yLORayGyKN8WBQVOChp44NxTITfG4bRZZ6anBIKaQIwVHlCzsk+NtjV hlGeeg7pyRolFpuRC7JNBSdAxjyj/kMWiBwQdIqwmZHklCeo+bW52eW+dJBDxuyw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id EFCC17E3E0; Wed, 14 Feb 2018 05:59:23 -0500 (EST) From: Thomas Monjalon To: Erik Gabriel Carrillo Cc: dev@dpdk.org, nhorman@tuxdriver.com, pbhagavatula@caviumnetworks.com, aconole@redhat.com Date: Wed, 14 Feb 2018 11:59:12 +0100 Message-ID: <9001700.V5d3VI6AvN@xps> In-Reply-To: <5006829.4uDuJ5LzRD@xps> References: <1515789935-3794-1-git-send-email-erik.g.carrillo@intel.com> <5006829.4uDuJ5LzRD@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 1/1] doc: announce API change to lcore role function 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: , X-List-Received-Date: Wed, 14 Feb 2018 10:59:24 -0000 14/02/2018 01:09, Thomas Monjalon: > 12/01/2018 21:45, Erik Gabriel Carrillo: > > This an API/ABI change notice for DPDK 18.05 announcing a change in > > the meaning of the return values of the rte_lcore_has_role() function. > > > > Signed-off-by: Erik Gabriel Carrillo > > --- > > +* eal: The semantics of the return value for the ``rte_lcore_has_role`` function > > + are planned to change in v18.05. The function currently returns 0 and <0 for > > + success and failure, respectively. This will change to 1 and 0 for true and > > + false, respectively, to make use of the function more intuitive. > > It will introduce some subtle bugs in applications. > We must clearly advertise this API change in the release notes. > > Acked-by: Thomas Monjalon Applied