From: Dan Williams <dan.j.williams@intel.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>
Subject: Re: arch/powerpc/mm/book3s64/pgtable.c:174:15: error: no previous prototype for 'create_section_mapping'
Date: Mon, 23 Nov 2020 19:20:46 -0800 [thread overview]
Message-ID: <CAPcyv4hoGYDro_JKUtKv+A69u=+2rKdfkACmNR6ndb-ZXGJsDw@mail.gmail.com> (raw)
In-Reply-To: <202011241003.eYk8XbNj-lkp@intel.com>
On Mon, Nov 23, 2020 at 6:13 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: d5beb3140f91b1c8a3d41b14d729aefa4dcc58bc
> commit: a927bd6ba952d13c52b8b385030943032f659a3e mm: fix phys_to_target_node() and memory_add_physaddr_to_nid() exports
> date: 31 hours ago
> config: powerpc-randconfig-r024-20201123 (attached as .config)
> compiler: powerpc64le-linux-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a927bd6ba952d13c52b8b385030943032f659a3e
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout a927bd6ba952d13c52b8b385030943032f659a3e
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=powerpc
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> >> arch/powerpc/mm/book3s64/pgtable.c:174:15: error: no previous prototype for 'create_section_mapping' [-Werror=missing-prototypes]
> 174 | int __meminit create_section_mapping(unsigned long start, unsigned long end,
> | ^~~~~~~~~~~~~~~~~~~~~~
> arch/powerpc/mm/book3s64/pgtable.c:405:6: error: no previous prototype for 'arch_report_meminfo' [-Werror=missing-prototypes]
> 405 | void arch_report_meminfo(struct seq_file *m)
> | ^~~~~~~~~~~~~~~~~~~
> arch/powerpc/mm/book3s64/pgtable.c:461:5: error: no previous prototype for 'pmd_move_must_withdraw' [-Werror=missing-prototypes]
> 461 | int pmd_move_must_withdraw(struct spinlock *new_pmd_ptl,
> | ^~~~~~~~~~~~~~~~~~~~~~
> cc1: all warnings being treated as errors
>
> vim +/create_section_mapping +174 arch/powerpc/mm/book3s64/pgtable.c
The whack-a-mole continues... the kbuild-robot success report I
received gave me too much confidence.
next prev parent reply other threads:[~2020-11-24 3:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 2:12 arch/powerpc/mm/book3s64/pgtable.c:174:15: error: no previous prototype for 'create_section_mapping' kernel test robot
2020-11-24 3:20 ` Dan Williams [this message]
2020-11-24 5:45 ` Philip Li
-- strict thread matches above, loose matches on Subject: below --
2021-11-09 18:59 kernel test robot
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='CAPcyv4hoGYDro_JKUtKv+A69u=+2rKdfkACmNR6ndb-ZXGJsDw@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.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;
as well as URLs for NNTP newsgroup(s).