From: Minchan Kim <minchan@kernel.org>
To: kbuild test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
sfr@canb.auug.org.au
Subject: Re: [linux-next:master] BUILD REGRESSION 30e2206e11ce27ae910cc0dab21472429e400a87
Date: Sat, 9 May 2020 15:31:14 -0700 [thread overview]
Message-ID: <20200509223114.GB61301@google.com> (raw)
In-Reply-To: <5eb7081c.tF8Lx9jHI/dmVqqk%lkp@intel.com>
On Sun, May 10, 2020 at 03:44:28AM +0800, kbuild test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> branch HEAD: 30e2206e11ce27ae910cc0dab21472429e400a87 Add linux-next specific files for 20200508
>
> Error/Warning in current branch:
>
> /usr/bin/ld: drivers/net/ethernet/xilinx/ll_temac_main.c:1411: undefined reference to `devm_ioremap'
> <stdin>:1520:2: warning: #warning syscall process_madvise not implemented [-Wcpp]
> arch/riscv/mm/ptdump.c:210:20: error: implicit declaration of function 'pte_pfn' [-Werror=implicit-function-declaration]
> arch/riscv/mm/ptdump.c:257:6: error: 'KERN_VIRT_START' undeclared (first use in this function); did you mean 'KERN_VIRT_SIZE'?
> arch/riscv/mm/ptdump.c:257:6: warning: initialization of 'long unsigned int' from 'struct addr_marker *' makes integer from pointer without a cast [-Wint-conversion]
> arch/riscv/mm/ptdump.c:57:3: error: 'FIXADDR_START' undeclared here (not in a function); did you mean 'XAS_RESTART'?
> arch/riscv/mm/ptdump.c:58:3: error: 'FIXADDR_TOP' undeclared here (not in a function)
> arch/riscv/mm/ptdump.c:59:3: error: 'PCI_IO_START' undeclared here (not in a function)
> arch/riscv/mm/ptdump.c:60:3: error: 'PCI_IO_END' undeclared here (not in a function)
> arch/x86/hyperv/hv_apic.o: warning: objtool: hv_apic_write()+0x97: alternative modifies stack
> drivers/infiniband/sw/rxe/rxe_queue.c:69 do_mmap_info() warn: maybe return -EFAULT instead of the bytes remaining?
> drivers/net/ethernet/xilinx/ll_temac_main.c:1411: undefined reference to `devm_ioremap'
>
> Error/Warning ids grouped by kconfigs:
>
> recent_errors
> |-- i386-allyesconfig
> | `-- drivers-infiniband-sw-rxe-rxe_queue.c-do_mmap_info()-warn:maybe-return-EFAULT-instead-of-the-bytes-remaining
> |-- mips-allmodconfig
> | `-- stdin:warning:warning-syscall-process_madvise-not-implemented
> |-- mips-allnoconfig
> | `-- stdin:warning:warning-syscall-process_madvise-not-implemented
> |-- mips-allyesconfig
> | `-- stdin:warning:warning-syscall-process_madvise-not-implemented
> |-- mips-maltasmvp_defconfig
> | `-- stdin:warning:warning-syscall-process_madvise-not-implemented
> |-- mips-randconfig-r006-20200509
> | `-- stdin:warning:warning-syscall-process_madvise-not-implemented
For process_madvivse part for mips was merged into mmotm and it will
land on Monday for linux-next.
Thanks, kbuild test rebot.
prev parent reply other threads:[~2020-05-09 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 19:44 kbuild test robot
2020-05-09 22:31 ` Minchan Kim [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=20200509223114.GB61301@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=sfr@canb.auug.org.au \
/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