On Mon, 11 Aug 2025 17:56:55 -0700 Jakub Kicinski <kuba@xxxxxxxxxx> wrote: > On Mon, 11 Aug 2025 11:28:45 -0600 Jonathan Corbet wrote: > > Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx> writes: > > > That's the v10 version of the parser-yaml series, addressing a couple of > > > issues raised by Donald. > > > > > > It should apply cleanly on the top of docs-next, as I just rebased on > > > the top of docs/docs-next. > > > > > > Please merge it via your tree, as I have another patch series that will > > > depend on this one. > > > > I intend to do that shortly unless I hear objections; are the netdev > > folks OK with this work going through docs-next? > > No objections. > > Would you be willing to apply these on top of -rc1, and create a merge > commit? YNL is fairly active, if there's a conflict we may be testing > our luck if Linus has to resolve Python conflicts. > > Happy to do that on our end (we have a script:)), or perhaps Mauro could > apply and send us both a PR? Whatever works best for you. In case you decide for the PR, I'm sending one right now for you both. It is on a stable signed tag: https://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-docs.git/tag/?h=docs/v6.17-1 So, if both of you pick from it, we should be able to avoid conflicts on the next merge window, as I don't have any patches changing the Sphinx yaml parser plugin nor netlink tools. It should be noticed that I have a patch series that does a major cleanup at Documentation/Makefile. It is based after this series. So, better to have the series merged at linux-docs to avoid merge conflicts at linux-next and during the next merge window. Thanks, Mauro
