From: kernel test robot <lkp@intel.com>
To: Nick Hu <nick.hu@sifive.com>,
paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, leyfoon.tan@starfivetech.com,
mason.huo@starfivetech.com, conor.dooley@microchip.com,
jeeheng.sia@starfivetech.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, zong.li@sifive.com
Cc: oe-kbuild-all@lists.linux.dev, Andy Chiu <andy.chiu@sifive.com>
Subject: Re: [PATCH v2] riscv: suspend: Add syscore ops for suspend
Date: Wed, 23 Aug 2023 02:06:01 +0800 [thread overview]
Message-ID: <202308230107.1L1ahyas-lkp@intel.com> (raw)
In-Reply-To: <20230822054739.33552-1-nick.hu@sifive.com>
Hi Nick,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.5-rc7 next-20230822]
[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/Nick-Hu/riscv-suspend-Add-syscore-ops-for-suspend/20230822-135024
base: linus/master
patch link: https://lore.kernel.org/r/20230822054739.33552-1-nick.hu%40sifive.com
patch subject: [PATCH v2] riscv: suspend: Add syscore ops for suspend
config: riscv-randconfig-r121-20230822 (https://download.01.org/0day-ci/archive/20230823/202308230107.1L1ahyas-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230823/202308230107.1L1ahyas-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/202308230107.1L1ahyas-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/riscv/kernel/suspend.c: In function 'riscv_cpu_resume':
>> arch/riscv/kernel/suspend.c:114:25: warning: unused variable 'regs' [-Wunused-variable]
114 | struct pt_regs *regs = task_pt_regs(cur_task);
| ^~~~
vim +/regs +114 arch/riscv/kernel/suspend.c
110
111 static void riscv_cpu_resume(void)
112 {
113 struct task_struct *cur_task = get_current();
> 114 struct pt_regs *regs = task_pt_regs(cur_task);
115
116 if (has_fpu())
117 fstate_restore(cur_task, regs);
118 if (has_vector())
119 riscv_v_vstate_restore(cur_task, regs);
120 }
121
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-08-22 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 5:47 [PATCH v2] riscv: suspend: Add syscore ops for suspend Nick Hu
2023-08-22 6:16 ` Anup Patel
2023-08-22 7:58 ` Nick Hu
2023-08-22 9:17 ` Anup Patel
2023-08-23 3:08 ` Nick Hu
2023-08-23 13:44 ` Anup Patel
2023-08-28 3:33 ` Nick Hu
2023-08-22 18:06 ` 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=202308230107.1L1ahyas-lkp@intel.com \
--to=lkp@intel.com \
--cc=andy.chiu@sifive.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=jeeheng.sia@starfivetech.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mason.huo@starfivetech.com \
--cc=nick.hu@sifive.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=zong.li@sifive.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