From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ebiederm-user-namespace:signal-for-v5.17 10/12] kernel/kthread.c:299: warning: expecting prototype for kthread_complete_and exit(). Prototype was for kthread_complete_and_exit() instead
Date: Tue, 14 Dec 2021 13:47:58 +0800 [thread overview]
Message-ID: <202112141329.KBkyJ5ql-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git signal-for-v5.17
head: 6b1248798eb6f6d5285db214299996ecc5dc1e6b
commit: cead18552660702a4a46f58e65188fe5f36e9dfe [10/12] exit: Rename complete_and_exit to kthread_complete_and_exit
config: x86_64-randconfig-a011-20211213 (https://download.01.org/0day-ci/archive/20211214/202112141329.KBkyJ5ql-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/commit/?id=cead18552660702a4a46f58e65188fe5f36e9dfe
git remote add ebiederm-user-namespace https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
git fetch --no-tags ebiederm-user-namespace signal-for-v5.17
git checkout cead18552660702a4a46f58e65188fe5f36e9dfe
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
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 >>):
>> kernel/kthread.c:299: warning: expecting prototype for kthread_complete_and exit(). Prototype was for kthread_complete_and_exit() instead
vim +299 kernel/kthread.c
285
286 /**
287 * kthread_complete_and exit - Exit the current kthread.
288 * @comp: Completion to complete
289 * @code: The integer value to return to kthread_stop().
290 *
291 * If present complete @comp and the reuturn code to kthread_stop().
292 *
293 * A kernel thread whose module may be removed after the completion of
294 * @comp can use this function exit safely.
295 *
296 * Does not return.
297 */
298 void __noreturn kthread_complete_and_exit(struct completion *comp, long code)
> 299 {
300 if (comp)
301 complete(comp);
302
303 kthread_exit(code);
304 }
305 EXPORT_SYMBOL(kthread_complete_and_exit);
306
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [ebiederm-user-namespace:signal-for-v5.17 10/12] kernel/kthread.c:299: warning: expecting prototype for kthread_complete_and exit(). Prototype was for kthread_complete_and_exit() instead
Date: Tue, 14 Dec 2021 13:47:58 +0800 [thread overview]
Message-ID: <202112141329.KBkyJ5ql-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git signal-for-v5.17
head: 6b1248798eb6f6d5285db214299996ecc5dc1e6b
commit: cead18552660702a4a46f58e65188fe5f36e9dfe [10/12] exit: Rename complete_and_exit to kthread_complete_and_exit
config: x86_64-randconfig-a011-20211213 (https://download.01.org/0day-ci/archive/20211214/202112141329.KBkyJ5ql-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/commit/?id=cead18552660702a4a46f58e65188fe5f36e9dfe
git remote add ebiederm-user-namespace https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
git fetch --no-tags ebiederm-user-namespace signal-for-v5.17
git checkout cead18552660702a4a46f58e65188fe5f36e9dfe
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
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 >>):
>> kernel/kthread.c:299: warning: expecting prototype for kthread_complete_and exit(). Prototype was for kthread_complete_and_exit() instead
vim +299 kernel/kthread.c
285
286 /**
287 * kthread_complete_and exit - Exit the current kthread.
288 * @comp: Completion to complete
289 * @code: The integer value to return to kthread_stop().
290 *
291 * If present complete @comp and the reuturn code to kthread_stop().
292 *
293 * A kernel thread whose module may be removed after the completion of
294 * @comp can use this function exit safely.
295 *
296 * Does not return.
297 */
298 void __noreturn kthread_complete_and_exit(struct completion *comp, long code)
> 299 {
300 if (comp)
301 complete(comp);
302
303 kthread_exit(code);
304 }
305 EXPORT_SYMBOL(kthread_complete_and_exit);
306
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2021-12-14 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 5:47 kernel test robot [this message]
2021-12-14 5:47 ` [ebiederm-user-namespace:signal-for-v5.17 10/12] kernel/kthread.c:299: warning: expecting prototype for kthread_complete_and exit(). Prototype was for kthread_complete_and_exit() instead kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-12-14 6:42 kernel test robot
2021-12-14 6:42 ` kernel test robot
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=202112141329.KBkyJ5ql-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.