From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Frederic Weisbecker <frederic@kernel.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 18:33:38 -0800 [thread overview]
Message-ID: <20250112183338.0ac4e721a48829afffd16073@linux-foundation.org> (raw)
In-Reply-To: <c883110c-6baf-410e-8a77-4c2501060375@infradead.org>
On Sun, 12 Jan 2025 10:21:40 -0800 Randy Dunlap <rdunlap@infradead.org> wrote:
> >
> > 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.
It appears to be a fix against Frederic's b1e125dcbcea ("kthread: Unify
kthread_create_on_cpu() and kthread_create_worker_on_cpu() automatic
format") so it would best be carried in whatever tree holds
b1e125dcbcea.
From: Randy Dunlap <rdunlap@infradead.org>
Subject: kthread: modify kernel-doc function name to match code
Date: Fri, 10 Jan 2025 22:30:08 -0800
kthread.c:1073: warning: expecting prototype for kthread_create_worker(). Prototype was for kthread_create_worker_on_node() instead
Link: https://lkml.kernel.org/r/20250111063008.910712-1-rdunlap@infradead.org
Fixes: b1e125dcbcea ("kthread: Unify kthread_create_on_cpu() and kthread_create_worker_on_cpu() automatic format")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/kthread.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/kthread.c~kthread-modify-kernel-doc-function-name-to-match-code
+++ a/kernel/kthread.c
@@ -900,7 +900,7 @@ fail_task:
}
/**
- * kthread_create_worker - create a kthread worker
+ * kthread_create_worker_on_node - create a kthread worker
* @flags: flags modifying the default behavior of the worker
* @namefmt: printf-style name for the kthread worker (task).
*
_
next prev parent reply other threads:[~2025-01-13 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 14:37 [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 kernel test robot
2025-01-12 18:21 ` Randy Dunlap
2025-01-13 2:33 ` Andrew Morton [this message]
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=20250112183338.0ac4e721a48829afffd16073@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=frederic@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox