From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 2/2] ethdev: pre-emptively document rte_eth_dev_reset error code Date: Tue, 24 Oct 2017 14:29:30 +0200 Message-ID: <4520525.jkYRCSMrae@xps> References: <20171019134827.22740-1-luca.boccassi@gmail.com> <20171024110312.24029-1-luca.boccassi@gmail.com> <20171024110312.24029-2-luca.boccassi@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, wenzhuo.lu@intel.com, wei.dai@intel.com, remy.horton@intel.com To: luca.boccassi@gmail.com, Luca Boccassi Return-path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 97E781B766 for ; Tue, 24 Oct 2017 14:29:31 +0200 (CEST) In-Reply-To: <20171024110312.24029-2-luca.boccassi@gmail.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 24/10/2017 13:03, luca.boccassi@gmail.com: > From: Luca Boccassi > > When VF reset will be supported by drivers, the API will most likely > have to return -EAGAIN to avoid blocking when the VF cannot be reset > because the PF is down. > Document it immediately even if it's not yet supported, so that users > and developers can already take into account about this use case, and > thus avoid an API-incompatible change later on. > > This is based on real-world production usage and customer escalations, > using earlier patches from Intel. > > Signed-off-by: Luca Boccassi Suggested title: "ethdev: document new error code for reset" Acked-by: Thomas Monjalon