linux-kernel - Re: [PATCH v10 00/14] Don't generate netlink .rst files inside $(srctree)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250812112950.0de576fc@foz.lan>
Date: Tue, 12 Aug 2025 11:29:50 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Jonathan Corbet <corbet@....net>, Linux Doc Mailing List
 <linux-doc@...r.kernel.org>, linux-kernel@...r.kernel.org, Akira Yokosawa
 <akiyks@...il.com>, "David S. Miller" <davem@...emloft.net>, Ignacio
 Encinas Rubio <ignacio@...cinas.com>, Marco Elver <elver@...gle.com>, Shuah
 Khan <skhan@...uxfoundation.org>, Donald Hunter <donald.hunter@...il.com>,
 Eric Dumazet <edumazet@...gle.com>, Jan Stancek <jstancek@...hat.com>,
 Paolo Abeni <pabeni@...hat.com>, Ruben Wauters <rubenru09@....com>,
 joel@...lfernandes.org, linux-kernel-mentees@...ts.linux.dev,
 lkmm@...ts.linux.dev, netdev@...r.kernel.org, peterz@...radead.org,
 stern@...land.harvard.edu, Breno Leitao <leitao@...ian.org>, Randy Dunlap
 <rdunlap@...radead.org>, Simon Horman <horms@...nel.org>
Subject: Re: [PATCH v10 00/14] Don't generate netlink .rst files inside
 $(srctree)

On Mon, 11 Aug 2025 17:56:55 -0700
Jakub Kicinski <kuba@...nel.org> wrote:

> On Mon, 11 Aug 2025 11:28:45 -0600 Jonathan Corbet wrote:
> > Mauro Carvalho Chehab <mchehab+huawei@...nel.org> 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