From: Nathan Chancellor <nathan@kernel.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, Mike Rapoport <rppt@linux.ibm.com>,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] mm/gfp: Add kernel-doc for gfp_t
Date: Fri, 19 Feb 2021 12:55:09 -0700 [thread overview]
Message-ID: <20210219195509.GA59987@24bbad8f3778> (raw)
In-Reply-To: <20210215204909.3824509-1-willy@infradead.org>
On Mon, Feb 15, 2021 at 08:49:09PM +0000, Matthew Wilcox (Oracle) wrote:
> The generated html will link to the definition of the gfp_t automatically
> once we define it. Move the one-paragraph overview of GFP flags from the
> documentation directory into gfp.h and pull gfp.h into the documentation.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
This patch causes a clang warning in basically every file on linux-next
now:
include/linux/gfp.h:20:32: warning: redefinition of typedef 'gfp_t' is a C11 feature [-Wtypedef-redefinition]
typedef unsigned int __bitwise gfp_t; // repeated here for kernel-doc
^
include/linux/types.h:148:32: note: previous definition is here
typedef unsigned int __bitwise gfp_t;
^
1 warning generated.
Cheers,
Nathan
next prev parent reply other threads:[~2021-02-19 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 20:49 Matthew Wilcox (Oracle)
2021-02-15 21:07 ` Mike Rapoport
2021-02-19 19:55 ` Nathan Chancellor [this message]
2021-02-19 20:54 ` Matthew Wilcox
2021-02-19 21:45 ` Nick Desaulniers
2021-02-19 22:15 ` Miguel Ojeda
2021-02-19 22:49 ` Nick Desaulniers
2021-02-20 9:43 ` Miguel Ojeda
2021-02-22 17:04 ` Nick Desaulniers
2021-02-22 17:16 ` Matthew Wilcox
2021-02-22 17:34 ` Nick Desaulniers
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=20210219195509.GA59987@24bbad8f3778 \
--to=nathan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.com \
--cc=willy@infradead.org \
/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