From: "Tobin C. Harding" <me@tobin.cc>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mike Rapoport <rppt@linux.ibm.com>,
"Tobin C. Harding" <tobin@kernel.org>,
Christopher Lameter <cl@linux.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/3] docs: Use underscore not hyphen in label
Date: Wed, 6 Feb 2019 15:27:55 +1100 [thread overview]
Message-ID: <20190206042755.GC16761@eros.localdomain> (raw)
In-Reply-To: <c19a1a84-72cd-407a-f4f1-180c5b0d4bf0@darmarit.de>
On Tue, Feb 05, 2019 at 09:30:46AM +0100, Markus Heiser wrote:
> Am 05.02.19 um 00:03 schrieb Jonathan Corbet:
> > On Tue, 5 Feb 2019 08:12:20 +1100
> > "Tobin C. Harding" <me@tobin.cc> wrote:
> >
> > > I tried to investigate this further and I am unable to reproduce the
> > > original warning. I'm using python virtual environment as directed by
> > > the output of `make htmldocs` so the environment should not have
> > > changed. The only other plausible explanation seems to be that I've
> > > gone mad and can't remember what I was doing three days ago.
> >
> > You are not the first to have reported such issues, though; I've seen a
> > couple of things go by in the past. Until we understand what is going on,
> > it's probably best to avoid hyphens in labels.
This statement is not sitting well with me Jon, we are using hyphens in
labels all over the place with *almost* no issue. Seems we either
change them all or none of them. (FTR I think we should not change any
of them.)
> Many errors are not reported again in rebuilds.
It's more than that. Seems that no .o files means dependencies are not
the same in docs directories to *usual* source code directories, as in
this example, a file with an outdated label was not rebuilt since it
wasn't touched.
Note to self, always do clean build for docs patches. Thanks.
> To reproduce this error run 'make cleandocs htmldocs' first. Then you will see
> this error message (I'am on current docs-next from Jon using Sphinx v1.8.3 ):
>
> Documentation/core-api/mm-api.rst:22: WARNING: undefined label: \
> memory-allocation (if the link has no caption ...)
Can confirm I also get this warning, sloppy work by me I missed one
label. Second note to self, grep the whole tree not just /Documentation
Thanks for reporting this.
> In mm-api.rst you find this include:
>
> .. kernel-doc:: include/linux/slab.h
> :internal:
>
>
> And in slab.h you see a kmalloc DOC with a :ref:`..<memory-allocation>`
>
>
> /**
> * kmalloc - allocate memory
> * @size: how many bytes of memory are required.
> * @flags: the type of memory to allocate.
> *
> * kmalloc is the normal method of allocating memory
> * for objects smaller than page size in the kernel.
> *
> * The @flags argument may be one of the GFP flags defined at
> * include/linux/gfp.h and described at
> * :ref:`Documentation/core-api/mm-api.rst <mm-api-gfp-flags>`
> *
> * The recommended usage of the @flags is described at
> * :ref:`Documentation/core-api/memory-allocation.rst <memory-allocation>`
>
>
> With Tobin's patch applied to Jon's docs-next (cd7198fc959), this error comes up
> the first time (for me).
>
> Can we please revert cd7198fc959 / Thanks
I agree with you Markus, I'd like to see this reverted. Jon, your the
boss, if you want this patch to stay I can send in a patch to fix the
undefined label that this patch misses.
> @Tobin can you pleases test to revert cd7198fc959 and make a full build with
> 'cleandocs' first .. may this error comes up again for you and we can
> investigate any further .. if this depends to sphinx-Version or what ever.
With patch reverted, on docs-next, I've got 0 'undefined labels'
warnings.
Hope this adds more help than confusion :)
Tobin
next prev parent reply other threads:[~2019-02-06 4:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 4:06 [PATCH 0/3] docs: vm: Fix typo and build warnings Tobin C. Harding
2019-01-31 4:06 ` [PATCH 1/3] docs: Fix SLUB docs typo Tobin C. Harding
2019-01-31 9:30 ` Mike Rapoport
2019-01-31 4:06 ` [PATCH 2/3] docs: Add missing colon Tobin C. Harding
2019-01-31 9:30 ` Mike Rapoport
2019-01-31 4:06 ` [PATCH 3/3] docs: Use underscore not hyphen in label Tobin C. Harding
2019-01-31 9:27 ` Mike Rapoport
2019-01-31 20:56 ` Tobin C. Harding
2019-02-01 23:03 ` Jonathan Corbet
2019-02-02 14:32 ` Mike Rapoport
2019-02-03 23:20 ` Tobin C. Harding
2019-02-04 8:38 ` Mike Rapoport
2019-02-04 21:12 ` Tobin C. Harding
2019-02-04 23:03 ` Jonathan Corbet
2019-02-05 8:30 ` Markus Heiser
2019-02-06 4:27 ` Tobin C. Harding [this message]
2019-02-06 7:49 ` Markus Heiser
2019-02-06 20:28 ` Tobin C. Harding
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=20190206042755.GC16761@eros.localdomain \
--to=me@tobin.cc \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=markus.heiser@darmarit.de \
--cc=rppt@linux.ibm.com \
--cc=tobin@kernel.org \
/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