From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Nathan Chancellor <nathan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Mike Rapoport <rppt@linux.ibm.com>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] mm/gfp: Add kernel-doc for gfp_t
Date: Sat, 20 Feb 2021 10:43:52 +0100 [thread overview]
Message-ID: <CANiq72m6C0U8nG6jaWu4jMa3yzMepGYzwyH-eEufOxCnjy86BA@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdmo+5oBGcLsboZDQo_qtT9uusXjD5OPtu8isRuUUZ+ysw@mail.gmail.com>
On Fri, Feb 19, 2021 at 11:50 PM Nick Desaulniers
<ndesaulniers@google.com> wrote:
>
> (There is a separate warning flag for broken header guards,
> -Wheader-guard:
> https://github.com/ClangBuiltLinux/linux/issues?q=is%3Aissue+label%3A-Wheader-guard+is%3Aclosed)
Yeah, this would still help cases with headers without guards (not
really common, but...).
> What happens should the kernel move to gnu11, as discussed once GCC
> 5.1+ becomes the minimum supported version for all arches?
> https://lore.kernel.org/lkml/CAHk-=whnKkj5CSbj-uG_MVVUsPZ6ppd_MFhZf_kpXDkh2MAVRA@mail.gmail.com/
>
> Then the warning will not fire, since it's only really meant to help C
> code be portable between -std=c11.
I think it is a fine warning to keep in the compiler nevertheless
since you already have it, even if disabled by default or only in
-Wextra or something like that -- e.g. I would use it in my own
projects since I never intend to redefine a typedef.
> https://lore.kernel.org/linux-mm/20210215204909.3824509-1-willy@infradead.org/
Thanks for the link!
Cheers,
Miguel
next prev parent reply other threads:[~2021-02-20 9:44 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
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 [this message]
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=CANiq72m6C0U8nG6jaWu4jMa3yzMepGYzwyH-eEufOxCnjy86BA@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-mm@kvack.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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