From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Russell King <rmk+kernel@armlinux.org.uk>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [kbuild-all] Re: arch/arm/boot/compressed/fdt_check_mem_start.c:62:10: warning: no previous prototype for 'fdt_check_mem_start'
Date: Thu, 11 Nov 2021 13:43:17 +0800 [thread overview]
Message-ID: <b0050723-5ff4-0cea-0607-f7616037e4a3@intel.com> (raw)
In-Reply-To: <CAMuHMdUXYv8eSd6FY5JzjZ9bR1sfGT4jgwdj4qvD6heG9ue7Mw@mail.gmail.com>
On 11/10/2021 5:36 PM, Geert Uytterhoeven wrote:
> Hi Kernel Test Robot,
>
> On Wed, Nov 10, 2021 at 1:39 AM kernel test robot <lkp@intel.com> wrote:
>> FYI, the error/warning still remains.
>
> Indeed, and currently there are no plans to fix that.
> Please add it to the ignorelist.
Hi Geert,
Thanks for the feedback, we'll ignore the warning.
Best Regards,
Rong Chen
>
> Thanks!
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: cb690f5238d71f543f4ce874aa59237cf53a877c
>> commit: 0673cb38951215060d7993b43ad3c45cd413c2c3 ARM: 9045/1: uncompress: Validate start of physical memory against passed DTB
>> date: 9 months ago
>> config: arm-randconfig-r022-20210927 (attached as .config)
>> compiler: arm-linux-gnueabi-gcc (GCC) 11.2.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=0673cb38951215060d7993b43ad3c45cd413c2c3
>> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> git fetch --no-tags linus master
>> git checkout 0673cb38951215060d7993b43ad3c45cd413c2c3
>> # save the attached .config to linux build tree
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=arm
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>> All warnings (new ones prefixed by >>):
>>
>>>> arch/arm/boot/compressed/fdt_check_mem_start.c:62:10: warning: no previous prototype for 'fdt_check_mem_start' [-Wmissing-prototypes]
>> 62 | uint32_t fdt_check_mem_start(uint32_t mem_start, const void *fdt)
>> | ^~~~~~~~~~~~~~~~~~~
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
>
prev parent reply other threads:[~2021-11-11 5:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 0:38 kernel test robot
2021-11-10 9:36 ` Geert Uytterhoeven
2021-11-11 5:43 ` Chen, Rong A [this message]
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=b0050723-5ff4-0cea-0607-f7616037e4a3@intel.com \
--to=rong.a.chen@intel.com \
--cc=ardb@kernel.org \
--cc=geert@linux-m68k.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rmk+kernel@armlinux.org.uk \
/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
all inboxes | Powered by JetHome®