From: Thomas Monjalon <thomas@monjalon.net>
To: Liron Himi <lironh@marvell.com>
Cc: David Marchand <david.marchand@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"dev@dpdk.org" <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 [thread overview]
Message-ID: <3786530.kQq0lBPeGt@thomas> (raw)
In-Reply-To: <PH0PR18MB447327133A44809E2427E2EDC6669@PH0PR18MB4473.namprd18.prod.outlook.com>
29/11/2021 10:55, Liron Himi:
> From: Thomas Monjalon <thomas@monjalon.net>
> 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/
next prev parent reply other threads:[~2021-11-29 10:10 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 6:23 [dpdk-dev] [PATCH] common/cnxk: add REE support lironh
2021-10-28 9:30 ` Jerin Jacob
2021-11-23 19:13 ` [PATCH v2 0/5] regex/cn9k: use cnxk infrastructure lironh
2021-11-23 19:13 ` [PATCH v2 1/5] common/cnxk: add REE HW definitions lironh
2021-11-23 19:13 ` [PATCH v2 2/5] common/cnxk: add REE mbox definitions lironh
2021-11-23 19:13 ` [PATCH v2 3/5] common/cnxk: add REE support lironh
2021-11-23 19:13 ` [PATCH v2 4/5] common/cnxk: link REE support to ROC files lironh
2021-11-23 19:13 ` [PATCH v2 5/5] regex/cn9k: use cnxk infrastructure lironh
[not found] ` <20211123193835.20601-1-robot@bytheb.org>
2021-11-28 20:17 ` [EXT] |FAILURE| pw104631 " Liron Himi
2021-11-28 20:37 ` Thomas Monjalon
2021-11-29 9:55 ` Liron Himi
2021-11-29 10:10 ` Thomas Monjalon [this message]
2021-11-29 19:47 ` [PATCH v2 0/5] " lironh
2021-11-29 19:47 ` [PATCH v3 " lironh
2021-11-29 19:47 ` [PATCH v3 1/5] common/cnxk: add REE HW definitions lironh
2021-12-07 18:31 ` [PATCH v4 0/4] regex/cn9k: use cnxk infrastructure lironh
2021-12-07 18:31 ` [PATCH v4 1/4] common/cnxk: add REE HW definitions lironh
2021-12-07 18:31 ` [PATCH v4 2/4] common/cnxk: add REE mbox definitions lironh
2021-12-07 18:31 ` [PATCH v4 3/4] common/cnxk: add REE support lironh
2021-12-07 18:31 ` [PATCH v4 4/4] regex/cn9k: use cnxk infrastructure lironh
2021-12-08 9:14 ` [PATCH v4 0/4] " Jerin Jacob
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 0/5] remove octeontx2 drivers jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 1/5] common/cnxk: add REE HW definitions jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 2/5] common/cnxk: add REE mbox definitions jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 3/5] common/cnxk: add REE support jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 4/5] regex/cn9k: use cnxk infrastructure jerinj
2021-12-11 9:04 ` [dpdk-dev] [PATCH v5 5/5] drivers: remove octeontx2 drivers jerinj
2021-12-14 8:57 ` Ruifeng Wang
2022-01-12 14:37 ` [dpdk-dev] [PATCH v5 0/5] " Thomas Monjalon
2021-11-29 19:47 ` [PATCH v3 2/5] common/cnxk: add REE mbox definitions lironh
2021-11-29 19:47 ` [PATCH v3 3/5] common/cnxk: add REE support lironh
2021-11-29 19:47 ` [PATCH v3 4/5] common/cnxk: link REE support to ROC files lironh
2021-11-29 19:47 ` [PATCH v3 5/5] regex/cn9k: use cnxk infrastructure lironh
2021-11-29 19:49 ` [PATCH v3 0/5] " lironh
2021-11-29 19:49 ` [PATCH v3 1/5] common/cnxk: add REE HW definitions lironh
2021-11-29 19:49 ` [PATCH v3 2/5] common/cnxk: add REE mbox definitions lironh
2021-11-29 19:49 ` [PATCH v3 3/5] common/cnxk: add REE support lironh
2021-11-29 19:49 ` [PATCH v3 4/5] common/cnxk: link REE support to ROC files lironh
2021-11-29 19:49 ` [PATCH v3 5/5] regex/cn9k: use cnxk infrastructure lironh
2021-11-29 19:59 ` [PATCH v3 0/5] " lironh
2021-11-29 19:59 ` [PATCH v3 1/5] common/cnxk: add REE HW definitions lironh
2021-11-29 19:59 ` [PATCH v3 2/5] common/cnxk: add REE mbox definitions lironh
2021-11-29 19:59 ` [PATCH v3 3/5] common/cnxk: add REE support lironh
2021-11-29 19:59 ` [PATCH v3 4/5] common/cnxk: link REE support to ROC files lironh
2021-12-06 5:07 ` Jerin Jacob
2021-12-06 6:54 ` [EXT] " Liron Himi
2021-12-06 8:08 ` Jerin Jacob
2021-11-29 19:59 ` [PATCH v3 5/5] regex/cn9k: use cnxk infrastructure lironh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3786530.kQq0lBPeGt@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=lironh@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).