All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Alistair Francis <alistair.francis@wdc.com>
Cc: kbuild-all@lists.01.org,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
	linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmer@rivosinc.com>,
	Anup Patel <anup@brainfault.org>, Guo Ren <guoren@kernel.org>
Subject: [ammarfaizi2-block:palmer/linux/riscv-asidlen 1/1] arch/riscv/mm/context.c:308:45: error: 'mm_context_t' has no member named 'id'
Date: Fri, 1 Apr 2022 22:54:55 +0800	[thread overview]
Message-ID: <202204012242.MvKAyz37-lkp@intel.com> (raw)

tree:   https://github.com/ammarfaizi2/linux-block palmer/linux/riscv-asidlen
head:   bdfae0d4f28854d02d1f78fcb18b41d01ae32832
commit: bdfae0d4f28854d02d1f78fcb18b41d01ae32832 [1/1] riscv: Ensure only ASIDLEN is used for sfence.vma
config: riscv-nommu_k210_defconfig (https://download.01.org/0day-ci/archive/20220401/202204012242.MvKAyz37-lkp@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/ammarfaizi2/linux-block/commit/bdfae0d4f28854d02d1f78fcb18b41d01ae32832
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block palmer/linux/riscv-asidlen
        git checkout bdfae0d4f28854d02d1f78fcb18b41d01ae32832
        # 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 arch/riscv/mm/

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

   arch/riscv/mm/context.c: In function 'get_mm_asid':
>> arch/riscv/mm/context.c:308:45: error: 'mm_context_t' has no member named 'id'
     308 |         return atomic_long_read(&mm->context.id) & asid_mask;
         |                                             ^
>> arch/riscv/mm/context.c:308:52: error: 'asid_mask' undeclared (first use in this function); did you mean 'pid_task'?
     308 |         return atomic_long_read(&mm->context.id) & asid_mask;
         |                                                    ^~~~~~~~~
         |                                                    pid_task
   arch/riscv/mm/context.c:308:52: note: each undeclared identifier is reported only once for each function it appears in
   arch/riscv/mm/context.c:309:1: error: control reaches end of non-void function [-Werror=return-type]
     309 | }
         | ^
   cc1: some warnings being treated as errors


vim +308 arch/riscv/mm/context.c

   305	
   306	unsigned long get_mm_asid(struct mm_struct *mm)
   307	{
 > 308		return atomic_long_read(&mm->context.id) & asid_mask;
   309	}
   310	

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

                 reply	other threads:[~2022-04-01 15:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202204012242.MvKAyz37-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alistair.francis@wdc.com \
    --cc=anup@brainfault.org \
    --cc=guoren@kernel.org \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=palmer@rivosinc.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 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.