Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs

2020-04-16 Thread Jani Nikula
On Fri, 20 Mar 2020, Jonathan Corbet wrote: > On Fri, 20 Mar 2020 16:11:01 +0100 > Mauro Carvalho Chehab wrote: > >> This small series address a regression caused by a new patch at >> docs-next (and at linux-next). > > I don't know how I missed that mess, sorry. I plead distracting times or >

Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs

2020-04-08 Thread Mauro Carvalho Chehab
Em Tue, 07 Apr 2020 13:46:23 +1000 Michael Ellerman escreveu: > Mauro Carvalho Chehab writes: > > This small series address a regression caused by a new patch at > > docs-next (and at linux-next). > > ... > > This solves almost all problems we have. Still, there are a few places > > where we

Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs

2020-04-06 Thread Michael Ellerman
Mauro Carvalho Chehab writes: > This small series address a regression caused by a new patch at > docs-next (and at linux-next). > > Before this patch, when a cross-reference to a chapter within the > documentation is needed, we had to add a markup like: > > .. _foo: > > foo >

Re: [PATCH v2 0/2] Don't generate thousands of new warnings when building docs

2020-03-20 Thread Jonathan Corbet
On Fri, 20 Mar 2020 16:11:01 +0100 Mauro Carvalho Chehab wrote: > This small series address a regression caused by a new patch at > docs-next (and at linux-next). I don't know how I missed that mess, sorry. I plead distracting times or something like that. Heck, I think I'll blame everything

[PATCH v2 0/2] Don't generate thousands of new warnings when building docs

2020-03-20 Thread Mauro Carvalho Chehab
This small series address a regression caused by a new patch at docs-next (and at linux-next). Before this patch, when a cross-reference to a chapter within the documentation is needed, we had to add a markup like: .. _foo: foo === This behavor is now different after