[PATCH v5 1/4] dts: add start Tx first method to testpmd shell
David Marchand
david.marchand at redhat.com
Wed Jan 21 11:04:07 CET 2026
Hello Patrick,
On Tue, 20 Jan 2026 at 17:46, Patrick Robb <probb at iol.unh.edu> wrote:
>
> Hi David,
>
> Dean and I both looked at the patch from Lukas, yes it looks good and I will add a comment and tag there.
>
> Otherwise, I'm not sure how the patch could have been breaking docs given our process. Can you please sanity check my process below? Maybe I am making a silly mistake with validating the docs build.
>
> For the next dts branch, when I'm adding new patches, for each patch:
>
> 1. Apply patchseries
> 2. Run normal checks (checkpatches.sh, check-git-log.sh, dts-check-format.sh)
> 3. Perform a doc build like below:
>
> meson setup my-doc-build
> ninja -C my-doc-build doc
>
> Then, It quickly does a doc build, and (although I don't always look unless I'm making a docs change) it is possible to navigate into the build dir docs dir, and open up the html docs files.
>
> 4. Then at the end I push my local branch with the new patches added to the remote next-dts repo.
>
> So, is my above docs check sufficient, or am I missing a part of the process?
As part of this process, I assume that you look at reports for the
series in patchwork.
This looks correct then.
To be honest, I can not see the warnings myself locally (running Fedora 42 atm).
I guess there is a difference in Ubuntu 22.04 sphinx, that is used in GHA.
However, we let doc warnings for dts go unnoticed, and this should be changed.
I sent a patch for this:
https://patchwork.dpdk.org/project/dpdk/patch/20260121100127.1701459-1-david.marchand@redhat.com/
--
David Marchand
More information about the dev
mailing list