From: Randy Dunlap <rdunlap@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-nonmm-unstable 171/173] kernel/kthread.c:913: warning: expecting prototype for kthread_create_worker_on_node(). Prototype was for kthread_create_worker() instead
Date: Sun, 12 Jan 2025 10:21:40 -0800 [thread overview]
Message-ID: <c883110c-6baf-410e-8a77-4c2501060375@infradead.org> (raw)
In-Reply-To: <202501122249.upmy4970-lkp@intel.com>
Hi ktr, Andrew,
On 1/12/25 6:37 AM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
> head: dfbe2aeb5ed491cb9f0a2de5a7ad9a9d4d477a8f
> commit: 1bc3c5db9becd0171108c2dcfaf7ef5ef10c1e03 [171/173] kthread: modify kernel-doc function name to match code
> config: i386-buildonly-randconfig-001-20250112 (https://download.01.org/0day-ci/archive/20250112/202501122249.upmy4970-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250112/202501122249.upmy4970-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/202501122249.upmy4970-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
>>> kernel/kthread.c:913: warning: expecting prototype for kthread_create_worker_on_node(). Prototype was for kthread_create_worker() instead
>
>
> vim +913 kernel/kthread.c
>
> fbae2d44aa1df7 Petr Mladek 2016-10-11 901
> fbae2d44aa1df7 Petr Mladek 2016-10-11 902 /**
> 1bc3c5db9becd0 Randy Dunlap 2025-01-10 903 * kthread_create_worker_on_node - create a kthread worker
> dbf52682cb0286 Petr Mladek 2016-10-11 904 * @flags: flags modifying the default behavior of the worker
> fbae2d44aa1df7 Petr Mladek 2016-10-11 905 * @namefmt: printf-style name for the kthread worker (task).
> fbae2d44aa1df7 Petr Mladek 2016-10-11 906 *
> fbae2d44aa1df7 Petr Mladek 2016-10-11 907 * Returns a pointer to the allocated worker on success, ERR_PTR(-ENOMEM)
> fbae2d44aa1df7 Petr Mladek 2016-10-11 908 * when the needed structures could not get allocated, and ERR_PTR(-EINTR)
> d25c83c6606ffc Petr Mladek 2022-03-15 909 * when the caller was killed by a fatal signal.
> fbae2d44aa1df7 Petr Mladek 2016-10-11 910 */
> fbae2d44aa1df7 Petr Mladek 2016-10-11 911 struct kthread_worker *
> dbf52682cb0286 Petr Mladek 2016-10-11 912 kthread_create_worker(unsigned int flags, const char namefmt[], ...)
> fbae2d44aa1df7 Petr Mladek 2016-10-11 @913 {
@Andrew: I don't know how to handle this. My patch applies correctly to linux-next
where this function name has been changed. It looks like 0day is applying it
to mainline linux + your tree(s?) for testing.
--
~Randy
next prev parent reply other threads:[~2025-01-12 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 14:37 kernel test robot
2025-01-12 18:21 ` Randy Dunlap [this message]
2025-01-13 2:33 ` Andrew Morton
2025-01-13 10:39 ` Frederic Weisbecker
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=c883110c-6baf-410e-8a77-4c2501060375@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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