From: Petr Mladek <pmladek@suse.com>
To: Chris Down <chris@chrisdown.name>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: [PATCH] printk/documentation: Update printk()/_printk() documentation
Date: Fri, 23 Jul 2021 13:24:05 +0200 [thread overview]
Message-ID: <YPqm1XpFIcOjBQsl@alley> (raw)
In-Reply-To: <YPqjdqSH5j69FnHV@alley>
On Fri 2021-07-23 13:09:43, Petr Mladek wrote:
> The commit 337015573718b161 ("printk: Userspace format indexing support")
> caused the following warning when building htmldocs:
>
> kernel/printk/printk.c:1: warning: 'printk' not found
>
> The problem is that printk() became a macro that is defined
> in include/linux/printk.h instead of kernel/printk.c. The original
> function was renamed to _printk().
>
> Fixes: 337015573718b161 ("printk: Userspace format indexing support")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Petr Mladek <pmladek@suse.com>
> Link: https://lore.kernel.org/r/YPbBfdz9srIpI+bb@chrisdown.name
> ---
> This should do the trick. I do not longer see the warning.
And I have just pushed it together with the other fixes into
printk/linux.git, branch for-5.15-printk-index.
Best Regards,
Petr
next prev parent reply other threads:[~2021-07-23 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 6:24 linux-next: build warning after merge of the printk tree Stephen Rothwell
2021-07-20 12:18 ` 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 [this message]
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
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=YPqm1XpFIcOjBQsl@alley \
--to=pmladek@suse.com \
--cc=chris@chrisdown.name \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.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