public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 3/3] mm/mempolicy: wire up syscall set_mempolicy_home_node
Date: Thu, 21 Oct 2021 11:31:13 +0530	[thread overview]
Message-ID: <2815d79c-7c0f-01df-4f61-d11aa8b2012a@linux.ibm.com> (raw)
In-Reply-To: <202110210302.HqL0ETus-lkp@intel.com>

On 10/21/21 00:54, kernel test robot wrote:
> Hi "Aneesh,
> 
> [FYI, it's a private test report for your RFC patch.]
> [auto build test WARNING on arm64/for-next/core]
> [also build test WARNING on linus/master v5.15-rc6]
> [cannot apply to hnaz-mm/master tip/x86/asm next-20211020]
> [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/Aneesh-Kumar-K-V/mm-mempolicy-use-policy_node-helper-with-MPOL_PREFERRED_MANY/20211020-172721
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> config: arm64-randconfig-r033-20211019 (attached as .config)
> compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 9660563950aaed54020bfdf0be07e7096a9553e4)
> 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 arm64 cross compiling tool for clang build
>          # apt-get install binutils-aarch64-linux-gnu
>          # https://github.com/0day-ci/linux/commit/10f30e8157782f17ae682c2bbca95c226af3612a
>          git remote add linux-review https://github.com/0day-ci/linux
>          git fetch --no-tags linux-review Aneesh-Kumar-K-V/mm-mempolicy-use-policy_node-helper-with-MPOL_PREFERRED_MANY/20211020-172721
>          git checkout 10f30e8157782f17ae682c2bbca95c226af3612a
>          # save the attached .config to linux build tree
>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm64
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All warnings (new ones prefixed by >>):
> 
>             asmlinkage long __weak __arm64_sys_##name(const struct pt_regs *regs)   \
>                                    ^
>     <scratch space>:60:1: note: expanded from here
>     __arm64_sys_process_madvise
>     ^
>     kernel/sys_ni.c:291:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
>     arch/arm64/include/asm/syscall_wrapper.h:76:13: note: expanded from macro 'COND_SYSCALL'
>             asmlinkage long __weak __arm64_sys_##name(const struct pt_regs *regs)   \
>                        ^

Is this clang specific? I am not able to recreate this with gcc 10 cross 
compiling.

-aneesh

  reply	other threads:[~2021-10-21  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211020092453.179929-3-aneesh.kumar@linux.ibm.com>
2021-10-20 19:24 ` [RFC PATCH v2 3/3] mm/mempolicy: wire up syscall set_mempolicy_home_node kernel test robot
2021-10-21  6:01   ` Aneesh Kumar K.V [this message]
2021-10-21 16:44     ` Nick Desaulniers

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=2815d79c-7c0f-01df-4f61-d11aa8b2012a@linux.ibm.com \
    --to=aneesh.kumar@linux.ibm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    /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