From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Hellwig <hch@lst.de>,
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 pstore tree
Date: Tue, 15 Jun 2021 08:36:56 -0700 [thread overview]
Message-ID: <202106150833.1F1D7E5A@keescook> (raw)
In-Reply-To: <20210615201516.56c760fa@canb.auug.org.au>
On Tue, Jun 15, 2021 at 08:15:16PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the pstore tree, today's linux-next build (htmldocs)
> produced this warning:
>
> fs/pstore/blk.c:1: warning: no structured comments found
>
> Introduced by commit
>
> 38c18fec13fb ("pstore/blk: Use the normal block device I/O path")
>
> The last kernedoc comment in this file is removed by this commit.
I was briefly quite confused by this. I see now it's the
:internal: not the :export: use of blk.c. If it's possible to
improve this error report email with more details in the future,
that would be nice. For example, "blk.c:1" isn't helpful, but
"Documentation/admin-guide/pstore-blk.rst:230" would be. :)
I'll get this fixed up; thanks!
-Kees
--
Kees Cook
next prev parent reply other threads:[~2021-06-15 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 10:15 linux-next: build warning after merge of the pstore tree Stephen Rothwell
2021-06-15 15:36 ` Kees Cook [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-16 0:27 Stephen Rothwell
2016-11-16 0:35 ` Kees Cook
2016-11-16 5:19 ` Joel Fernandes
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=202106150833.1F1D7E5A@keescook \
--to=keescook@chromium.org \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).