public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Gurbir Arora <gurbaror@codeaurora.org>,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, bjorn.andersson@linaro.org,
	mathieu.poirier@linaro.org, tsoni@codeaurora.org,
	psodagud@codeaurora.org, sidgup@codeaurora.org,
	rishabhb@codeaurora.org, Gurbir Arora <gurbaror@codeaurora.org>
Subject: Re: [PATCH v2 2/3] remoteproc: qcom: Add capability to collect minidumps
Date: Thu, 3 Sep 2020 20:09:18 +0800	[thread overview]
Message-ID: <202009032024.5QYL2eBs%lkp@intel.com> (raw)
In-Reply-To: <1599101516-243760-3-git-send-email-gurbaror@codeaurora.org>

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

Hi Gurbir,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.9-rc3 next-20200903]
[cannot apply to linux/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/Gurbir-Arora/Introduce-mini-dump-support-for-remoteproc/20200903-105359
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git fc3abb53250a90ba2150eebd182137c136f4d25a
config: nds32-randconfig-r026-20200902 (attached as .config)
compiler: nds32le-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
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=nds32 

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 >>):

   nds32le-linux-ld: drivers/remoteproc/remoteproc_coredump.o: in function `qcom_rproc_minidump':
   remoteproc_coredump.c:(.text+0x346): undefined reference to `qcom_smem_get'
>> nds32le-linux-ld: remoteproc_coredump.c:(.text+0x34a): undefined reference to `qcom_smem_get'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

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

  parent reply	other threads:[~2020-09-03 12:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03  2:51 [PATCH v2 0/3] Introduce mini-dump support for remoteproc Gurbir Arora
2020-09-03  2:51 ` [PATCH v2 1/3] remoteproc: core: Add multiple components to remoteproc ops Gurbir Arora
2020-09-03  2:51 ` [PATCH v2 2/3] remoteproc: qcom: Add capability to collect minidumps Gurbir Arora
2020-09-03  8:20   ` kernel test robot
2020-09-03 12:09   ` kernel test robot [this message]
2020-09-03  2:51 ` [PATCH v2 3/3] remoteproc: qcom: Add minidump id for sm8150 modem remoteproc Gurbir Arora

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=202009032024.5QYL2eBs%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=gurbaror@codeaurora.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=psodagud@codeaurora.org \
    --cc=rishabhb@codeaurora.org \
    --cc=sidgup@codeaurora.org \
    --cc=tsoni@codeaurora.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