From: Mike Rapoport <rppt@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Karolina Drobnik <karolinadrobnik@gmail.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the memblock tree
Date: Thu, 10 Mar 2022 12:19:09 +0200 [thread overview]
Message-ID: <YinQncz54HIjp5HR@kernel.org> (raw)
In-Reply-To: <20220310211315.595cca09@canb.auug.org.au>
On Thu, Mar 10, 2022 at 09:13:15PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the memblock tree, today's linux-next build (KCONFIG_NAME)
> produced this warning:
>
> Documentation/vm/index.rst:12: WARNING: toctree contains reference to nonexisting document 'vm/memblock-sim'
>
> Introduced by commit
>
> cc5a1e382509 ("memblock tests: Add TODO and README files")
Huh, wrong git add, fixed now.
Thanks Stephen!
>
> --
> Cheers,
> Stephen Rothwell
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2022-03-10 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 10:13 linux-next: build warning after merge of the memblock tree Stephen Rothwell
2022-03-10 10:19 ` Mike Rapoport [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=YinQncz54HIjp5HR@kernel.org \
--to=rppt@kernel.org \
--cc=karolinadrobnik@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rppt@linux.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).