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 7FE37A0C58; Mon, 29 Nov 2021 11:10:27 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F0F2A4068A; Mon, 29 Nov 2021 11:10:26 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 483F740689 for ; Mon, 29 Nov 2021 11:10:25 +0100 (CET) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id D95915C00E7; Mon, 29 Nov 2021 05:10:24 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 29 Nov 2021 05:10:24 -0500 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=fm2; bh= ZyFz5ICP1NUjAqBpFa6blMGH8U2wdWoYl9RfnTMLaaY=; b=QE5k7eJRO3Mrx5Pm W2z67tmIeAv05d/eGcVMpBuno5AQLBIknIku36NMbjNiv/Ph7zezGIhTyV8dsxAa 8NfPOmbHMNe+dZuQfTfQBRASJyYxYKCSlehwzjlvjr4TQGIqVoHx7VMT42iNvImJ azjkzYMbCMo+kqOoPI8+D8CroXf2Ty8Gu42sNdzgyK/wkPliVyUK24zFLNBRugpy vzqMVJWj+6zJ83qYvQ1H9Py3uo8oVejJKIN45Y+y7QoN6eLTI3vl2SNRxeR29VMW IxC96fhhs8/2ORhPWuMPNtAP6GgWlKVDpXIQB+AOaUQ5nlj2tXZdbkZCpBDy5e2g 7IZUhw== 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=fm1; bh=ZyFz5ICP1NUjAqBpFa6blMGH8U2wdWoYl9RfnTMLa aY=; b=YDGvC2kUH/j/1qsAbfGQ1oRUsAFmnrVHuF+66YzYSXFvR09TG2ded/yOI goQB5NVG8SUzzmPF/9uYjZFBNhwjA4AgyjGOmA3CFIXaOGfJb4GsiNQE9ZDRoMeQ 5NqNXsNuU1OtkvNP7Qco5Yh7GXbp+BMG2pKmzpu+ZB2mvmojA2krr4rvVcMXg+T7 89Ls1agmjKDV+VZEQcbW2SXJzItuQ+3meJYfi3907Jj6IkaCG0KAtvlsCJ1LRwQM thPngrJxfv8Hb8mDcpWVVpIIlwOxWhIYckJvmmc90xDeKOMnO2uECRRz50ZNuE4i ZnC5LAQe3m9hBEw64w69KyZ1gQ18w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrheelgddufecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeffvdffjeeuteelfeeileduudeugfetjeelveefkeejfeeigeehteff vdekfeegudenucffohhmrghinhepughpughkrdhorhhgnecuvehluhhsthgvrhfuihiivg eptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdr nhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 29 Nov 2021 05:10:23 -0500 (EST) From: Thomas Monjalon To: Liron Himi Cc: David Marchand , "Yigit, Ferruh" , Jerin Jacob Kollanukkaran , "dev@dpdk.org" Subject: Re: [EXT] |FAILURE| pw104631 [PATCH v2 5/5] regex/cn9k: use cnxk infrastructure Date: Mon, 29 Nov 2021 11:10:22 +0100 Message-ID: <3786530.kQq0lBPeGt@thomas> In-Reply-To: References: <20211123191348.31239-6-lironh@marvell.com> <5922270.lOV4Wx5bFT@thomas> 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 29/11/2021 10:55, Liron Himi: > From: Thomas Monjalon > 28/11/2021 21:17, Liron Himi: > > Hi, > > > > I have fixed the error below but got additional errors which I need your advice if to ignore or update it is some way. > > This patch also replace the name of the 'regexdevs/octeontx2' folder to 'regexdevs/cn9k' > > Note that Jerin is going to remove the current 'octeontx2' references as the new cnxk is replacing it. > > > > What should I do with those errors: > > dpdk-next-net-mrvl/doc/guides/platform/octeontx2.rst:158:unknown document: ../regexdevs/octeontx2 > > This one, you must fix to the next regex doc. > [L.H.] okay. > > > dpdk-next-net-mrvl/doc/guides/rel_notes/release_20_11.rst:293:unknown document: ../regexdevs/octeontx2 > > This one, you must replace the link with a normal text. > For instance, this is what was done for another octeontx2 driver: > > - See the :doc:`../rawdevs/octeontx2_ep` for more details on this new PMD. > + See ``rawdevs/octeontx2_ep`` for more details on this new PMD. > [L.H.] but this file represent the release notes of dpdk-20.11, right? so, in this release the driver is still 'regexdevs/octeontx2'. > only in the upcoming release the driver name will be changed to "regexdevs/cn9k". > I also think this is relevant for the example you provided. In dpdk-20.11 the driver was "rawdevs/octeontx2_ep" In new releases, the driver doesn't exist, right? So the documentation, including old release notes cannot compile with a reference to a removed page. That's why we need to transform this link to a removed page. If you want to see the old documentation, you can go to https://doc.dpdk.org/guides-20.11/