public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Firoz Khan <firoz.khan@linaro.org>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
	linux-arch@vger.kernel.org, arnd@arndb.de,
	y2038@lists.linaro.org, Catalin Marinas <catalin.marinas@arm.com>,
	Philippe Ombredanne <pombredanne@nexb.com>,
	Will Deacon <will.deacon@arm.com>,
	linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>,
	marcin.juszkiewicz@linaro.org,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	kbuild-all@01.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	firoz.khan@linaro.org, Thomas Gleixner <tglx@linutronix.de>,
	linux-arm-kernel@lists.infradead.org, deepa.kernel@gmail.com
Subject: Re: [PATCH 3/3] arm64: generate uapi and kapi headers
Date: Sat, 5 Jan 2019 01:40:20 +0800	[thread overview]
Message-ID: <201901050132.nyKnIJSN%fengguang.wu@intel.com> (raw)
In-Reply-To: <1546530025-26014-4-git-send-email-firoz.khan@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]

Hi Firoz,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on v4.20 next-20190103]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Firoz-Khan/arm64-add-system-call-table-generation-files/20190104-105305
base:   https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        GCC_VERSION=7.2.0 make.cross ARCH=arm64 

All errors (new ones prefixed by >>):

>> make[2]: *** No rule to make target 'scripts/syscalls/syscall.tbl', needed by 'arch/arm64/include/generated/asm/syscall_table_64.h'.
>> make[2]: *** No rule to make target 'scripts/syscalltbl.sh', needed by 'arch/arm64/include/generated/asm/syscall_table_64.h'.
>> make[2]: *** No rule to make target 'scripts/syscallhdr.sh', needed by 'arch/arm64/include/generated/uapi/asm/unistd_32.h'.
>> make[2]: *** No rule to make target 'scripts/syscallnr.sh', needed by 'arch/arm64/include/generated/uapi/asm/unistd_nr_64.h'.
   make[2]: Target 'all' not remade because of errors.
   make[1]: *** [archheaders] Error 2
   make[1]: Target 'prepare' not remade because of errors.
   make: *** [sub-make] Error 2

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 61877 bytes --]

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-01-04 17:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 15:40 [PATCH 0/3] arm64: system call table generation for asm-generic Firoz Khan
2019-01-03 15:40 ` [PATCH 1/3] arm64: add system call table generation files Firoz Khan
2019-01-03 15:40 ` [PATCH 2/3] arm64: assign __NR_*_Linux_syscalls generated by the scripts Firoz Khan
2019-01-03 15:40 ` [PATCH 3/3] arm64: generate uapi and kapi headers Firoz Khan
2019-01-04 17:40   ` kbuild test robot [this message]
2019-01-19 23:56 ` [PATCH 0/3] arm64: system call table generation for asm-generic Will Deacon
2019-01-21 15:53   ` Arnd Bergmann
2019-01-22  4:17     ` Firoz Khan

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=201901050132.nyKnIJSN%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=deepa.kernel@gmail.com \
    --cc=firoz.khan@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=pombredanne@nexb.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=stefan@agner.ch \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.com \
    --cc=y2038@lists.linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox