public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Suren Baghdasaryan <surenb@google.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH 28/30] Improved symbolic error names
Date: Wed, 31 Aug 2022 10:46:17 +0800	[thread overview]
Message-ID: <202208311028.RMa7Foh1-lkp@intel.com> (raw)
In-Reply-To: <20220830214919.53220-29-surenb@google.com>

Hi Suren,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on linus/master]
[also build test ERROR on v6.0-rc3]
[cannot apply to vbabka-slab/for-next tip/sched/core xen-tip/linux-next next-20220830]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Suren-Baghdasaryan/Code-tagging-framework-and-applications/20220831-055155
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git dcf8e5633e2e69ad60b730ab5905608b756a032f
config: s390-randconfig-r044-20220830 (https://download.01.org/0day-ci/archive/20220831/202208311028.RMa7Foh1-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 1c66bacd6cde1f37d6ac96c45b389666a1334ec0)
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
        # install s390 cross compiling tool for clang build
        # apt-get install binutils-s390x-linux-gnu
        # https://github.com/intel-lab-lkp/linux/commit/8b71efada47e1ca3e6cb45ef71f3421ecff787df
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Suren-Baghdasaryan/Code-tagging-framework-and-applications/20220831-055155
        git checkout 8b71efada47e1ca3e6cb45ef71f3421ecff787df
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   s390x-linux-ld: DWARF error: invalid or unhandled FORM value: 0x23
   lib/errname.o: in function `errname_init':
>> errname.c:(.init.text+0x26): undefined reference to `codetag_register_type'
   s390x-linux-ld: drivers/pcmcia/cistpl.o: in function `release_cis_mem':
   cistpl.c:(.text+0x82): undefined reference to `iounmap'
   s390x-linux-ld: drivers/pcmcia/cistpl.o: in function `pcmcia_read_cis_mem':
   cistpl.c:(.text+0x19a): undefined reference to `ioremap'
   s390x-linux-ld: cistpl.c:(.text+0x21c): undefined reference to `iounmap'
   s390x-linux-ld: cistpl.c:(.text+0x22e): undefined reference to `ioremap'
   s390x-linux-ld: cistpl.c:(.text+0x2ee): undefined reference to `ioremap'
   s390x-linux-ld: cistpl.c:(.text+0x37a): undefined reference to `iounmap'
   s390x-linux-ld: cistpl.c:(.text+0x3ec): undefined reference to `iounmap'
   s390x-linux-ld: cistpl.c:(.text+0x3fe): undefined reference to `ioremap'
   s390x-linux-ld: drivers/pcmcia/cistpl.o: in function `pcmcia_write_cis_mem':
   cistpl.c:(.text+0x546): undefined reference to `ioremap'
   s390x-linux-ld: cistpl.c:(.text+0x5c2): undefined reference to `iounmap'
   s390x-linux-ld: cistpl.c:(.text+0x5d4): undefined reference to `ioremap'
   s390x-linux-ld: cistpl.c:(.text+0x692): undefined reference to `ioremap'
   s390x-linux-ld: cistpl.c:(.text+0x728): undefined reference to `iounmap'
   s390x-linux-ld: cistpl.c:(.text+0x758): undefined reference to `iounmap'
   s390x-linux-ld: cistpl.c:(.text+0x76a): undefined reference to `ioremap'

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

           reply	other threads:[~2022-08-31  2:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20220830214919.53220-29-surenb@google.com>]

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=202208311028.RMa7Foh1-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    --cc=surenb@google.com \
    /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