All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Prasad Sodagudi <psodagud@codeaurora.org>,
	rostedt@goodmis.org, mingo@redhat.com, keescook@chromium.org,
	saiprakash.ranjan@codeaurora.org
Cc: kbuild-all@lists.01.org, arnd@arndb.de,
	linux-arm-msm@vger.kernel.org, anton@enomsg.org,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] tracing: Add register read and write tracing support
Date: Mon, 28 Sep 2020 18:06:26 +0800	[thread overview]
Message-ID: <202009281853.hker3UWe%lkp@intel.com> (raw)
In-Reply-To: <1601253290-400618-2-git-send-email-psodagud@codeaurora.org>

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

Hi Prasad,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on tip/perf/core]
[also build test ERROR on trace/for-next arm64/for-next/core v5.9-rc7 next-20200925]
[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/Prasad-Sodagudi/tracing-Add-register-read-and-write-tracing-support/20200928-083807
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git a3b1e8451d3fd54fe0df661c2c4f983932b3c0bc
config: h8300-allyesconfig (attached as .config)
compiler: h8300-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
        # https://github.com/0day-ci/linux/commit/9048e77f99a2b88a28c7d4b6e51fe5c9ba30960d
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Prasad-Sodagudi/tracing-Add-register-read-and-write-tracing-support/20200928-083807
        git checkout 9048e77f99a2b88a28c7d4b6e51fe5c9ba30960d
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300 

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

   h8300-linux-ld: kernel/trace/trace.o: in function `.L1150':
>> trace.c:(.text+0x7305): undefined reference to `ftrace_trace_userstack'

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

WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] tracing: Add register read and write tracing support
Date: Mon, 28 Sep 2020 18:06:26 +0800	[thread overview]
Message-ID: <202009281853.hker3UWe%lkp@intel.com> (raw)
In-Reply-To: <1601253290-400618-2-git-send-email-psodagud@codeaurora.org>

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

Hi Prasad,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on tip/perf/core]
[also build test ERROR on trace/for-next arm64/for-next/core v5.9-rc7 next-20200925]
[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/Prasad-Sodagudi/tracing-Add-register-read-and-write-tracing-support/20200928-083807
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git a3b1e8451d3fd54fe0df661c2c4f983932b3c0bc
config: h8300-allyesconfig (attached as .config)
compiler: h8300-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
        # https://github.com/0day-ci/linux/commit/9048e77f99a2b88a28c7d4b6e51fe5c9ba30960d
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Prasad-Sodagudi/tracing-Add-register-read-and-write-tracing-support/20200928-083807
        git checkout 9048e77f99a2b88a28c7d4b6e51fe5c9ba30960d
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300 

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

   h8300-linux-ld: kernel/trace/trace.o: in function `.L1150':
>> trace.c:(.text+0x7305): undefined reference to `ftrace_trace_userstack'

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

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

  parent reply	other threads:[~2020-09-28 10:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28  0:34 [PATCH] Register read and writes tracing Prasad Sodagudi
2020-09-28  0:34 ` Prasad Sodagudi
2020-09-28  0:34 ` [PATCH] tracing: Add register read and write tracing support Prasad Sodagudi
2020-09-28  0:34   ` Prasad Sodagudi
2020-09-28  2:37   ` kernel test robot
2020-09-28  2:37     ` kernel test robot
2020-09-28  5:17   ` Greg KH
2020-09-28  5:17     ` Greg KH
2020-09-28  5:20   ` Greg KH
2020-09-28  5:20     ` Greg KH
2020-09-28 10:06   ` kernel test robot [this message]
2020-09-28 10:06     ` kernel test robot
2020-09-28 14:55   ` Steven Rostedt
2020-09-28 14:55     ` Steven Rostedt
2020-09-28  5:45 ` [PATCH] Register read and writes tracing Sai Prakash Ranjan
2020-09-28  5:45   ` Sai Prakash Ranjan

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=202009281853.hker3UWe%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=anton@enomsg.org \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=keescook@chromium.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=psodagud@codeaurora.org \
    --cc=rostedt@goodmis.org \
    --cc=saiprakash.ranjan@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 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.