From: Jonathan Corbet <corbet@lwn.net>
To: Mike Rapoport <rppt@kernel.org>
Cc: Mike Rapoport <rppt@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2 0/2] docs/mm: remove useless markup
Date: Tue, 31 Jan 2023 13:29:16 -0700 [thread overview]
Message-ID: <87357q4fdv.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230131144220.822989-1-rppt@kernel.org>
Mike Rapoport <rppt@kernel.org> writes:
> From: "Mike Rapoport (IBM)" <rppt@kernel.org>
>
> Hi,
>
> Following Jon's gripe about top-of-file labels [1], I went ahead and
> updated admin-guide/mm and mm docs to use file names instead of labels for
> document cross-referencing.
>
> [1] https://lore.kernel.org/all/87r0vh9n17.fsf@meer.lwn.net
This is a nice cleanup and I want to apply it, but it adds some
warnings:
> Documentation/mm/physical_memory.rst:61: WARNING: undefined label: page_migration
> Documentation/mm/physical_memory.rst:61: WARNING: undefined label: admin_guide_memory_hotplug
> Documentation/translations/zh_CN/mm/hmm.rst:251: WARNING: undefined label: page_migration
> Documentation/translations/zh_CN/mm/hugetlbfs_reserv.rst:18: WARNING: undefined label: hugetlbpage
> Documentation/translations/zh_CN/mm/numa.rst:76: WARNING: undefined label: numa_memory_policy
It looks like a few references didn't get fixed?
Thanks,
jon
prev parent reply other threads:[~2023-01-31 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 14:42 [PATCH v2 0/2] docs/mm: remove useless markup Mike Rapoport
2023-01-31 14:42 ` [PATCH v2 1/2] docs/admin-guide/mm: " Mike Rapoport
2023-01-31 14:42 ` [PATCH v2 2/2] docs/mm: " Mike Rapoport
2023-01-31 20:29 ` Jonathan Corbet [this message]
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=87357q4fdv.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.