From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Petr Mladek <pmladek@suse.com>
Cc: Chris Down <chris@chrisdown.name>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the printk tree
Date: Tue, 20 Jul 2021 16:24:23 +1000 [thread overview]
Message-ID: <20210720162423.75f61ce0@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
Hi all,
After merging the printk tree, today's linux-next build (htmldocs)
produced this warning:
kernel/printk/printk.c:1: warning: 'printk' not found
Introduced by commit
337015573718 ("printk: Userspace format indexing support")
I presume that "printk" is referred to elsewhere in the documentation
as being in this file.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-07-20 6:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 6:24 Stephen Rothwell [this message]
2021-07-20 12:18 ` linux-next: build warning after merge of the printk tree Chris Down
2021-07-20 12:22 ` Chris Down
2021-07-23 11:09 ` [PATCH] printk/documentation: Update printk()/_printk() documentation Petr Mladek
2021-07-23 11:24 ` Petr Mladek
2021-07-25 21:16 ` linux-next: build warning after merge of the printk tree Jonathan Corbet
2021-07-26 12:28 ` Petr Mladek
2021-07-26 13:07 ` Chris Down
-- strict thread matches above, loose matches on Subject: below --
2022-11-22 7:10 Stephen Rothwell
[not found] <CGME20180710064527epcas1p16fd9ad765711d69264b3251890bbcc2e@epcms5p5>
2018-07-10 6:45 ` Stephen Rothwell
2018-07-10 7:16 ` Maninder Singh
2018-07-10 9:19 ` Petr Mladek
2018-07-10 13:15 ` Sergey Senozhatsky
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=20210720162423.75f61ce0@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chris@chrisdown.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pmladek@suse.com \
/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