All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	SeongJae Park <sj@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the mm tree
Date: Wed, 21 Feb 2024 09:12:41 -0800	[thread overview]
Message-ID: <20240221171241.55658-1-sj@kernel.org> (raw)
In-Reply-To: <20240221162745.4332955c@canb.auug.org.au>

On Wed, 21 Feb 2024 16:27:45 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> --Sig_/rZSz2XyBy4/Li.uOi0DLWDM
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: quoted-printable
> 
> Hi all,
> 
> After merging the mm tree, today's linux-next build (htmldocs) produced
> these warnings:
> 
> Documentation/admin-guide/mm/damon/usage.rst:186: WARNING: undefined label:
>  'damon_design_confiurable_operations_set'
> Documentation/admin-guide/mm/damon/usage.rst:369: WARNING: undefined label:
>  'damon_design_damos_quota_auto_tuning'
> 
> Introduced by commits
> 
>   afc858f0e6db ("Docs/mm/damon: move DAMON operation sets list from the usage
> to the design document")
>   d50e871bd78b ("Docs/admin-guide/mm/damon/usage: document quota goal metric
> file")
> 
> from the mm-unstable branch of the mm tree.

Thank you for this nice report.  Just sent fixes:
https://lore.kernel.org/damon/20240221170852.55529-1-sj@kernel.org/


Thanks,
SJ

[...]

  reply	other threads:[~2024-02-21 17:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21  5:27 linux-next: build warnings after merge of the mm tree Stephen Rothwell
2024-02-21 17:12 ` SeongJae Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-05  9:42 Stephen Rothwell
2025-03-05  9:53 ` David Hildenbrand
2025-03-05 10:05   ` David Hildenbrand
2025-02-17  6:10 Stephen Rothwell
2025-02-17 16:28 ` Suren Baghdasaryan
2025-02-10  3:49 Stephen Rothwell
2025-02-09 23:06 Stephen Rothwell
2025-01-06  6:42 Stephen Rothwell
2024-09-11 10:21 Stephen Rothwell
2024-07-01  8:49 Stephen Rothwell
2024-07-02  3:14 ` Andrew Morton
2024-07-02  4:15   ` Jiaqi Yan
2024-07-02  4:33     ` Jiaqi Yan
2024-07-02  6:18       ` Andrew Morton
2024-07-02  6:37         ` Jiaqi Yan
2024-07-02 23:09           ` SeongJae Park
2024-07-02 23:55             ` Jiaqi Yan
2024-07-01  1:01 Stephen Rothwell
2024-07-01  1:13 ` Andrii Nakryiko
2024-07-01  8:28 ` Stephen Rothwell
2024-03-25  1:36 Stephen Rothwell
2024-03-26  2:19 ` Suren Baghdasaryan
2024-03-26  5:44   ` Randy Dunlap
2024-03-26  6:16     ` Suren Baghdasaryan
2024-03-28  4:39       ` Stephen Rothwell
2024-03-28  4:44         ` Stephen Rothwell
2024-03-28  5:35           ` Suren Baghdasaryan
2024-03-29 22:49             ` Stephen Rothwell
2024-03-29 23:01               ` Suren Baghdasaryan
2024-03-29 23:01                 ` Suren Baghdasaryan
2023-07-27  4:28 Stephen Rothwell
2023-07-27  4:46 ` Aneesh Kumar K.V
2023-07-27  5:00   ` Stephen Rothwell
2023-05-08  4:54 Stephen Rothwell
2023-05-08 16:10 ` Liam R. Howlett
2022-11-22  6:50 Stephen Rothwell
2022-08-23  3:54 Stephen Rothwell
2022-08-23 14:55 ` Liam Howlett
2022-05-11 10:20 Stephen Rothwell
2022-05-11 16:06 ` Johannes Weiner

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=20240221171241.55658-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.