All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC 2/2] Track io_ticks at microsecond granularity.
Date: Tue, 09 Jun 2020 14:36:45 +0800	[thread overview]
Message-ID: <202006091442.I2imbScG%lkp@intel.com> (raw)
In-Reply-To: <20200609040724.448519-3-joshs@netflix.com>

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

Hi Josh,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on block/for-next]
[cannot apply to linux/master v5.7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Josh-Snyder/Increase-accuracy-and-precision-of-sampled-io_ticks/20200609-120933
base:   https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: csky-defconfig (attached as .config)
compiler: csky-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=csky 

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 >>, old ones prefixed by <<):

csky-linux-ld: block/blk-core.o: in function `update_io_ticks.isra.0':
blk-core.c:(.text+0x870): undefined reference to `wrong_size_cmpxchg'
>> csky-linux-ld: blk-core.c:(.text+0x890): undefined reference to `wrong_size_cmpxchg'

---
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: 10060 bytes --]

  parent reply	other threads:[~2020-06-09  6:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-09  4:07 [RFC 0/2] Increase accuracy and precision of sampled io_ticks Josh Snyder
2020-06-09  4:07 ` [RFC 1/2] Eliminate over- and under-counting of io_ticks Josh Snyder
2020-06-09  8:08   ` Ming Lei
2020-06-10  1:41   ` Hou Tao
2020-06-10  7:26     ` Josh Snyder
2020-06-09  4:07 ` [RFC 2/2] Track io_ticks at microsecond granularity Josh Snyder
2020-06-09  6:23   ` kernel test robot
2020-06-09  6:36   ` kernel test robot [this message]
2020-06-09  8:50   ` Ming Lei

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=202006091442.I2imbScG%lkp@intel.com \
    --to=lkp@intel.com \
    --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.