mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	 Anup Patel <anup@brainfault.org>,
	Atish Patra <atishp@rivosinc.com>
Subject: Re: arch/riscv/kernel/paravirt.c:44:1: sparse: sparse: symbol '__pcpu_scope_steal_time' was not declared. Should it be static?
Date: Tue, 30 Jan 2024 13:18:04 +0100	[thread overview]
Message-ID: <20240130-630542897176b3dbc536657a@orel> (raw)
In-Reply-To: <202401301733.XLBqnyLY-lkp@intel.com>

On Tue, Jan 30, 2024 at 05:18:30PM +0800, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   861c0981648f5b64c86fd028ee622096eb7af05a
> commit: fdf68acccfc6af9497c34ee411d89af13b6516ed RISC-V: paravirt: Implement steal-time support
> date:   4 weeks ago
> config: riscv-randconfig-r133-20240130 (https://download.01.org/0day-ci/archive/20240130/202401301733.XLBqnyLY-lkp@intel.com/config)
> compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 4a39d08908942b2d415db405844cbe4af73e75d4)
> reproduce: (https://download.01.org/0day-ci/archive/20240130/202401301733.XLBqnyLY-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202401301733.XLBqnyLY-lkp@intel.com/
> 
> sparse warnings: (new ones prefixed by >>)
> >> arch/riscv/kernel/paravirt.c:44:1: sparse: sparse: symbol '__pcpu_scope_steal_time' was not declared. Should it be static?
>    arch/riscv/kernel/paravirt.c:106:19: sparse: sparse: cast to restricted __le32
>    arch/riscv/kernel/paravirt.c:107:30: sparse: sparse: restricted __le32 degrades to integer
>    arch/riscv/kernel/paravirt.c:102:26: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned int [usertype] sequence @@     got restricted __le32 @@
>    arch/riscv/kernel/paravirt.c:102:26: sparse:     expected unsigned int [usertype] sequence
>    arch/riscv/kernel/paravirt.c:102:26: sparse:     got restricted __le32
>    arch/riscv/kernel/paravirt.c:104:23: sparse: sparse: incorrect type in assignment (different base types) @@     expected unsigned long long [usertype] steal @@     got restricted __le64 @@
>    arch/riscv/kernel/paravirt.c:104:23: sparse:     expected unsigned long long [usertype] steal
>    arch/riscv/kernel/paravirt.c:104:23: sparse:     got restricted __le64
>    arch/riscv/kernel/paravirt.c:109:16: sparse: sparse: cast to restricted __le64
> 
> vim +/__pcpu_scope_steal_time +44 arch/riscv/kernel/paravirt.c
> 
>     43	
>   > 44	DEFINE_PER_CPU(struct sbi_sta_struct, steal_time) __aligned(64);
>     45	
> 
> -- 
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki

I wrote patches for these almost a month ago, but somehow forgot to post
them... I'll retest and post now.

Thanks,
drew

      reply	other threads:[~2024-01-30 12:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  9:18 kernel test robot
2024-01-30 12:18 ` Andrew Jones [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=20240130-630542897176b3dbc536657a@orel \
    --to=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=atishp@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@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

all inboxes | Powered by JetHome®