From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 71016A10DA for ; Fri, 2 Aug 2019 23:01:15 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 429E81C2ED; Fri, 2 Aug 2019 23:01:15 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 5345D1C2DE for ; Fri, 2 Aug 2019 23:01:13 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E425C220C9; Fri, 2 Aug 2019 17:01:12 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 02 Aug 2019 17:01:12 -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=zGFLxeNkO6UC3VcI1dJKKRwiSlYtbKJZlYS7goFmxsw=; b=FKn2OEdgFxtI 9vQxk2uWMdKVlMiiartjJDqdGVLFlC1pNwLDVe1ytqxNBZwWs09ipqRlwY31x0N/ TjwSj1UGJDtNBVS5p1d3fl4JPgJyZ2P+dlw+WcmlivVxiwfyQQq0B7qkXi1cJMgi jWe8XLmdrd/9nsq+H4kv3RXn/7QxyJo= 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=fm3; bh=zGFLxeNkO6UC3VcI1dJKKRwiSlYtbKJZlYS7goFmx sw=; b=JSuy7rkzsotf3r2hHFbUx6INC90XuAaG3ar5s105gp841PF3nRJ6WqkLw f2/6W0NEO0ot/YgjOgamdz3JMOpbRaeeHDs7XRd/rghayID8BV8T96WEu++iA9bH 7BFIFPLSG9imBoz9iSZ5QS/t2tQcZsa4P8uWtVPXe453sXSoGN1TbvyujUxlfLo3 vdf/YqCewwUqBXr10M9ZvMtAyn1vjRA97lsnoSn26+iEkvnA/G2jZHX8ZXiR2msU ZJOlCyDlaMmm4bwtTFKb4cvpQqeALuHNI9KursrGbCLq8ZHIJ0JCGuCwYq4Aux7C TmX2m8OHaA9VAKamGa54q9nRbsBNg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrleelgdduvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpehhuhgrrhhmrdgtohhmnecukfhppeejjedrudefgedrvddtfedrudekgeen ucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth enucevlhhushhtvghrufhiiigvpedt 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 57F1A380075; Fri, 2 Aug 2019 17:01:11 -0400 (EDT) From: Thomas Monjalon To: Phil Yang Cc: dev@dpdk.org, jgrajcia@cisco.com, anatoly.burakov@intel.com, ferruh.yigit@intel.com, gavin.hu@arm.com, honnappa.nagarahalli@arm.com, nd@arm.com Date: Fri, 02 Aug 2019 23:01:10 +0200 Message-ID: <4150673.WUjg2Ml5sm@xps> In-Reply-To: <1564655727-4142-1-git-send-email-phil.yang@arm.com> References: <1564655727-4142-1-git-send-email-phil.yang@arm.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] net/memif: fix multi-process device probe error 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" 01/08/2019 12:35, Phil Yang: > Fixes: c41a04958b ("net/memif: support multi-process") > > Signed-off-by: Phil Yang > Reviewed-by: Gavin Hu > --- > --- a/drivers/net/memif/rte_eth_memif.c > +++ b/drivers/net/memif/rte_eth_memif.c > @@ -1265,7 +1265,7 @@ rte_pmd_memif_probe(struct rte_vdev_device *vdev) > eth_dev->dev_ops = &ops; > eth_dev->device = &vdev->device; > eth_dev->rx_pkt_burst = eth_memif_rx; > - eth_dev->tx_pkt_burst = eth_memif_rx; > + eth_dev->tx_pkt_burst = eth_memif_tx; It is not a probe error, but malfunctioning device, right? What is the current behaviour? You could better explain the symptom in the commit log, and the root cause (typo).