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 88EE2A05D3 for ; Mon, 25 Mar 2019 15:29:16 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A27383195; Mon, 25 Mar 2019 15:29:15 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 937472BD3; Mon, 25 Mar 2019 15:29:14 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CF76E20354; Mon, 25 Mar 2019 10:29:13 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 25 Mar 2019 10:29:13 -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=6oBcQ6IHND8Voc2hzcvR2JpQMDKxvJ4ZhidTTmw+e0g=; b=dD0qcTi8J70r QDVNjHhu6Ymp2fdGUP6NIFGx//I1yxtP3MC100D3YGnbTC19HFuoWbEwohRXKuEp PKPci07v6W4k/BHJpmFiITWnbjb3xiCgE24j2pGLJFto4OCTUpkCayjmGcnoURiq OPSI5wp9rCtps9daSggsTuBXDp+g6cM= 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=6oBcQ6IHND8Voc2hzcvR2JpQMDKxvJ4ZhidTTmw+e 0g=; b=RWc8R3xstzKSAEykLHL5gdrBk+vzwlEcMYQAWLg3v7/zpe9eBFu31FeSX h5spcmqaJLeb6PA2qo4Ki9XqANR9wqOJM1jAGHE+DEE1wt0bo5fvQdchQRXpQJ1O TtbzyvuBpicvuagFCe6JPF1pDWB2gBOVspK9aGZFJi7Azuv0zgq8+rY3T3LaqKzT 9Mxw4tKDzLqZtXoOjBu7VScBVHG3xO+E8MKvapgQiR/yTACz314NklwDsEzp5kcr 7qqKKrFwa4l6CLxGOc4Zc9zK0kDppZt1fZVUGfhnMzU1Y0h/Tx+miG7Ys7N0ZNCi 5wgWoD43BiuSTiurKxXIn5oS8CscQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrjeekgdeijecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 352F0E46AB; Mon, 25 Mar 2019 10:29:12 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: Rami Rosen , dev@dpdk.org, konstantin.ananyev@intel.com, arybchenko@solarflare.com, stable@dpdk.org, John McNamara Date: Mon, 25 Mar 2019 15:29:10 +0100 Message-ID: <3378426.goBovEbrZ8@xps> In-Reply-To: <4ad956d8-597e-93f8-8318-f5a45c1cf8f1@intel.com> References: <20190322151753.6345-1-ramirose@gmail.com> <4ad956d8-597e-93f8-8318-f5a45c1cf8f1@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] ethdev: fix a typo 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: <20190325142910.3VxXgN_PycyuMSXPLVTzjmICY8UVSST_MMViTDHuVvE@z> 25/03/2019 15:16, Ferruh Yigit: > On 3/22/2019 3:17 PM, Rami Rosen wrote: > > This patch fixes a trivial typo in rte_ethdev.h. > > retieve=>retrieve > > > > Fixes: 80a1deb4c77a ("ethdev: add API to retrieve queue information") > > Cc: stable@dpdk.org > > > > Signed-off-by: Rami Rosen > > Reviewed-by: Ferruh Yigit > Applied to dpdk-next-net/master, thanks. > > > It is great to have these fixes, but I wonder if there is a way to get them > fixed as a bunch, can running a spell check utility on the DPDK and fix all > existing typos in one go help? Any idea? > > cc'ed John & Thomas, > Does it make sense to run something periodical, like before each release, run > spellcheck and fix the typos for whole code? Yes, it would make sense. We can also add more spell checkers as part of checkpatch.