oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Max Kellermann <max.kellermann@ionos.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Max Kellermann <max.kellermann@ionos.com>
Subject: Re: [PATCH 10/28] uprobes.h: move declarations to uprobes_types.h
Date: Sat, 3 Feb 2024 08:41:11 +0800	[thread overview]
Message-ID: <202402030843.CUng9PM7-lkp@intel.com> (raw)
In-Reply-To: <20240131145008.1345531-11-max.kellermann@ionos.com>

Hi Max,

kernel test robot noticed the following build errors:

[auto build test ERROR on next-20240131]
[cannot apply to mkp-scsi/for-next jejb-scsi/for-next axboe-block/for-next linus/master v6.8-rc2 v6.8-rc1 v6.7 v6.8-rc2]
[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/Max-Kellermann/include-add-missing-includes/20240131-231042
base:   next-20240131
patch link:    https://lore.kernel.org/r/20240131145008.1345531-11-max.kellermann%40ionos.com
patch subject: [PATCH 10/28] uprobes.h: move declarations to uprobes_types.h
config: csky-allnoconfig (https://download.01.org/0day-ci/archive/20240203/202402030843.CUng9PM7-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240203/202402030843.CUng9PM7-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/202402030843.CUng9PM7-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/csky/kernel/signal.c: In function 'do_notify_resume':
>> arch/csky/kernel/signal.c:259:17: error: implicit declaration of function 'uprobe_notify_resume'; did you mean 'do_notify_resume'? [-Werror=implicit-function-declaration]
     259 |                 uprobe_notify_resume(regs);
         |                 ^~~~~~~~~~~~~~~~~~~~
         |                 do_notify_resume
   cc1: some warnings being treated as errors


vim +259 arch/csky/kernel/signal.c

e9564df753fd54 Guo Ren 2018-09-05  250  
e9564df753fd54 Guo Ren 2018-09-05  251  /*
bf241682936293 Guo Ren 2019-04-01  252   * notification of userspace execution resumption
bf241682936293 Guo Ren 2019-04-01  253   * - triggered by the _TIF_WORK_MASK flags
e9564df753fd54 Guo Ren 2018-09-05  254   */
bf241682936293 Guo Ren 2019-04-01  255  asmlinkage void do_notify_resume(struct pt_regs *regs,
bf241682936293 Guo Ren 2019-04-01  256  	unsigned long thread_info_flags)
e9564df753fd54 Guo Ren 2018-09-05  257  {
8f6bb793b2be82 Guo Ren 2020-04-02  258  	if (thread_info_flags & _TIF_UPROBE)
8f6bb793b2be82 Guo Ren 2020-04-02 @259  		uprobe_notify_resume(regs);

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

           reply	other threads:[~2024-02-03  0:42 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240131145008.1345531-11-max.kellermann@ionos.com>]

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=202402030843.CUng9PM7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max.kellermann@ionos.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;
as well as URLs for NNTP newsgroup(s).