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: [PATCH v2] Fixed: Misaligned memory access. Fixed pointer comparison.
Date: Mon, 24 Jan 2022 21:38:59 +0800	[thread overview]
Message-ID: <202201242120.145V5gDs-lkp@intel.com> (raw)
In-Reply-To: <20220123034518.3717116-1-michael@michaelkloos.com>

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

Hi "Michael,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.17-rc1 next-20220124]
[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/Michael-T-Kloos/Fixed-Misaligned-memory-access-Fixed-pointer-comparison/20220123-115207
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 1c52283265a462a100ae63ddf58b4e5884acde86
config: riscv-allmodconfig (https://download.01.org/0day-ci/archive/20220124/202201242120.145V5gDs-lkp(a)intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.2.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/93c49cc1cc8a49ac3bc9233ec977a82ee3cf4ac6
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Michael-T-Kloos/Fixed-Misaligned-memory-access-Fixed-pointer-comparison/20220123-115207
        git checkout 93c49cc1cc8a49ac3bc9233ec977a82ee3cf4ac6
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash

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

   riscv64-linux-ld: arch/riscv/lib/memmove.o: in function `memmove':
>> (.text+0x4): multiple definition of `memmove'; mm/kasan/shadow.o:(.text+0x416): first defined here

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

      parent reply	other threads:[~2022-01-24 13:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23  3:45 [PATCH v2] Fixed: Misaligned memory access. Fixed pointer comparison Michael T. Kloos
2022-01-23  3:45 ` Michael T. Kloos
2022-01-23 13:31 ` David Laight
2022-01-23 13:31   ` David Laight
2022-01-23 16:53   ` Michael T. Kloos
2022-01-23 16:53     ` Michael T. Kloos
2022-01-23 22:35     ` David Laight
2022-01-23 22:35       ` David Laight
2022-01-23 23:03       ` Michael T. Kloos
2022-01-23 23:03         ` Michael T. Kloos
2022-01-23 15:44 ` Jessica Clarke
2022-01-23 15:44   ` Jessica Clarke
2022-01-23 17:15   ` Michael T. Kloos
2022-01-23 17:15     ` Michael T. Kloos
2022-01-24  9:21 ` David Laight
2022-01-24  9:21   ` David Laight
2022-01-24 19:19   ` Michael T. Kloos
2022-01-24 19:19     ` Michael T. Kloos
2022-01-24 22:28     ` David Laight
2022-01-24 22:28       ` David Laight
2022-01-24 13:38 ` kernel test robot [this message]

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=202201242120.145V5gDs-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.