mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: linux-next: build warnings after merge of the counters tree
Date: Wed, 28 Oct 2020 08:38:22 -0600	[thread overview]
Message-ID: <9b2593f6-b160-52d8-521e-3ad9b059d5a4@linuxfoundation.org> (raw)
In-Reply-To: <20201028142354.11d42e47@canb.auug.org.au>

On 10/27/20 9:23 PM, Stephen Rothwell wrote:
> Hi all,
> 
> On Wed, 28 Oct 2020 14:20:39 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>> After merging the counters tree, today's linux-next build (htmldocs)
>> produced these warnings:
>>
>>
>> Documentation/core-api/counters.rst:45: WARNING: undefined label: test counters module (if the link has no caption the label must precede a section header)
>> Documentation/core-api/counters.rst:48: WARNING: undefined label: selftest for counters (if the link has no caption the label must precede a section header)
>> Documentation/core-api/counters.rst:61: WARNING: undefined label: atomic_ops (if the link has no caption the label must precede a section header)
>>
>> Introduced by commit
>>
>>    37a0dbf631f6 ("counters: Introduce counter_atomic* counters")
> 
> Also:
> 
> Documentation/core-api/counters.rst: WARNING: document isn't included in any toctree
> 

Hi Stephen,

This patch series is still is progress. I will drop them from this
topic branch.

thanks,
-- Shuah

      reply	other threads:[~2020-10-28 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28  3:20 Stephen Rothwell
2020-10-28  3:23 ` Stephen Rothwell
2020-10-28 14:38   ` Shuah Khan [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=9b2593f6-b160-52d8-521e-3ad9b059d5a4@linuxfoundation.org \
    --to=skhan@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®