From: Randy Dunlap <rdunlap@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
clang-built-linux <clang-built-linux@googlegroups.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 5868/6773] arch/powerpc/mm/mem.c:91:12: warning: no previous prototype for function 'create_section_mapping'
Date: Wed, 18 Nov 2020 14:48:28 -0800 [thread overview]
Message-ID: <24515a61-61a9-0728-5ba1-cb2bf00bc449@infradead.org> (raw)
In-Reply-To: <CAPcyv4hrjj45kn9ep1mAAaX6vtA2+5x_67V-Da0kp7bO3HVa=g@mail.gmail.com>
On 11/18/20 1:38 PM, Dan Williams wrote:
> On Wed, Nov 18, 2020 at 1:20 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> [..]
>> Yes, so with gcc, that gave me something like 109 missing prototype
>> warnings -- including one for 'create_section_mapping'.
>
> You see those with this [1] applied? I don't see those warnings
> anymore with gcc-10.2.0 and that patch.
>
> [1]: http://lore.kernel.org/r/160558386174.2948926.2740149041249041764.stgit@dwillia2-desk3.amr.corp.intel.com
>
No, I was testing today's linux-next (20201118).
and gcc 7.5.0.
After applying that patch, that 1 out of 111 -Wmissing-prototype warnings
is gone. :)
Thanks.
next prev parent reply other threads:[~2020-11-18 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 12:26 kernel test robot
2020-11-18 19:22 ` Dan Williams
2020-11-18 19:52 ` Nick Desaulniers
2020-11-18 21:19 ` Randy Dunlap
2020-11-18 21:38 ` Dan Williams
2020-11-18 22:48 ` Randy Dunlap [this message]
2020-11-18 22:32 ` 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=24515a61-61a9-0728-5ba1-cb2bf00bc449@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.com \
--cc=tglx@linutronix.de \
/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