From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 148B6A0353; Thu, 24 Feb 2022 10:35:45 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9505541155; Thu, 24 Feb 2022 10:35:44 +0100 (CET) Received: from out4-smtp.messagingengine.com (unknown [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 835AC4114D for ; Thu, 24 Feb 2022 10:35:43 +0100 (CET) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 283165C03E0; Thu, 24 Feb 2022 04:35:37 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 24 Feb 2022 04:35:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; bh=kVQ4BMuAwG2gqN LFdN5uJz5MVii9DdcJlu6O/8HYpY8=; b=M/L/urLON/f6A/u3YpoCC4WMzq2j4P gBMWMl+FE1kpF55kU26XIuXN+X/fD6szzFGXbhOn5F07+QNO/PFJsRlrBQnz+0Lz KUw2QMXUdKXf/RvyC/Y5tsVU6NgZsbONN+ieubC4GIBQGXwX8hu3ST9GyAhu+nAA t5jg+1J+2NvTtBz730FL1sMvWlDx7y3NMTKIlOdDUoiGpnTsJwr3NYwSt3BKxVKG JYNo6lQSSKey5lRzTW7hhfLD0Pm+9SCyqkJFLDatT4aanvwnCINND93ZDaCBA73v t3YhdyjCb24XNbNDYRy4PqVOuqLfeY6HpuVy/TsxPb+an6WwWoUlz2/A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=kVQ4BMuAwG2gqNLFdN5uJz5MVii9DdcJlu6O/8HYp Y8=; b=AruiCPNDGblQILR+MYwcNSsojKwYII9XkP9cM/hmvb5GuSU+UTO/s2kl9 vtwWsDx+Qz58oHewFCLnrrHNbBoCmddjP0h89jWF4fPGoPWGa5rDTqpjrM4kOBgE ohipWP01QKf25F3Q3IacTF7o1pRbSV6hlfJEReD8IdgnKi6sMBB/1DoX7+hOYidk h3RN1iBoGvAyJFos3BoAN3QuDsrRsKXx6/gsRWVBuvNGcDIkXXGAllNz+QQzxxBY yyE6S10Gbgyc75s8bx8lDLQaUffJNL9mqCnEr81b6wF9yJZMAjF9qUPXzuaqPmRJ v2yJ9IK/ba69HorFOrnRQxobzW1CQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrledvgddthecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 24 Feb 2022 04:35:36 -0500 (EST) From: Thomas Monjalon To: Raslan Darawsheh Cc: dev@dpdk.org, ferruh.yigit@intel.com, Gal Cohen Subject: Re: [PATCH] devtools: add E-Switch keyword for commit checks Date: Thu, 24 Feb 2022 10:35:34 +0100 Message-ID: <5243139.Sb9uPGUboI@thomas> In-Reply-To: <20220224092623.26180-1-rasland@nvidia.com> References: <20220224092623.26180-1-rasland@nvidia.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 24/02/2022 10:26, Raslan Darawsheh: > This adds the syntax for E-Switch to have check on how > it suppose to be for commits [...] > +E-Switch It looks Mellanox people use this syntax in Linux kernel as well. Where does it come from? Is it a Mellanox-only wording? Intuitively, I would have written it eSwitch generally. It means "embedded switch", right?