From: Michael Ellerman <mpe@ellerman.id.au>
To: kbuild-all@lists.01.org
Subject: Re: [linuxppc:next-test 150/209] arch/powerpc/mm/book3s64/radix_pgtable.c:183:6: error: no previous prototype for 'radix__change_memory_range'
Date: Wed, 14 Apr 2021 21:36:20 +1000 [thread overview]
Message-ID: <87eefdrtcb.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <5fa303d2-404b-689e-aa2b-c7272d9f8f5a@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
Rong Chen <rong.a.chen@intel.com> writes:
> Hi Michael,
>
> On 4/13/21 9:53 PM, Michael Ellerman wrote:
>> kernel test robot <lkp@intel.com> writes:
>>> tree: https://github.com/linuxppc/linux next-test
>>> head: 7626ae32a84371a7790955cc086d1f570b2e14ba
>>> commit: bd573a81312fd9d6520b1cc81a88fd29e670e1ff [150/209] powerpc/mm/64s: Allow STRICT_KERNEL_RWX again
>>> config: powerpc-skiroot_defconfig (attached as .config)
>>> compiler: powerpc64le-linux-gcc (GCC) 9.3.0
>>> reproduce (this is a W=1 build):
>> ^^^^^^^^^^^^^^^^^^^
>>
>> I spent a while scratching my head over this one, before noticing this
>> little message that this is a W=1 build.
>>
>> Do you think you could make it more obvious that it's a W=1 build?
>
> Thanks for the feedback, we enabled W=1 by default for now, it looks
> silly if adding in the subject,
OK.
> so we have changed the reproduce command to show the option:
>
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross W=1 ARCH=powerpc
Nice, thanks!
cheers
prev parent reply other threads:[~2021-04-14 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 18:26 [linuxppc:next-test 150/209] arch/powerpc/mm/book3s64/radix_pgtable.c:183:6: error: no previous prototype for 'radix__change_memory_range' kernel test robot
2021-04-13 13:53 ` Michael Ellerman
2021-04-14 8:41 ` Rong Chen
2021-04-14 11:36 ` Michael Ellerman [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=87eefdrtcb.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.