From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
pmladek@suse.com, Qiang.Zhang@windriver.com, tglx@linutronix.de,
tj@kernel.org
Subject: [folded-merged] kthread_worker-document-cpu-hotplug-handling-fix.patch removed from -mm tree
Date: Mon, 14 Dec 2020 18:11:45 -0800 [thread overview]
Message-ID: <20201215021145.ZDQFDjQbJ%akpm@linux-foundation.org> (raw)
The patch titled
Subject: kthread_worker-document-cpu-hotplug-handling-fix
has been removed from the -mm tree. Its filename was
kthread_worker-document-cpu-hotplug-handling-fix.patch
This patch was dropped because it was folded into kthread_worker-document-cpu-hotplug-handling.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: kthread_worker-document-cpu-hotplug-handling-fix
grammar tweaks
Cc: Petr Mladek <pmladek@suse.com>
Cc: Tejun Heo <tj@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Zhang Qiang <Qiang.Zhang@windriver.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/kthread.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--- a/kernel/kthread.c~kthread_worker-document-cpu-hotplug-handling-fix
+++ a/kernel/kthread.c
@@ -795,11 +795,11 @@ EXPORT_SYMBOL(kthread_create_worker);
*
* CPU hotplug:
* The kthread worker API is simple and generic. It just provides a way
- * how to create, use, and destroy workers.
+ * to create, use, and destroy workers.
*
* It is up to the API user how to handle CPU hotplug. They have to decide
* how to handle pending work items, prevent queuing new ones, and
- * restore the functionality when the CPU goes off and on. There are
+ * restore the functionality when the CPU goes off and on. There are a
* few catches:
*
* - CPU affinity gets lost when it is scheduled on an offline CPU.
@@ -807,8 +807,8 @@ EXPORT_SYMBOL(kthread_create_worker);
* - The worker might not exist when the CPU was off when the user
* created the workers.
*
- * A good practice is to implement two CPU hotplug callbacks and
- * destroy/create the worker when CPU goes down/up.
+ * Good practice is to implement two CPU hotplug callbacks and to
+ * destroy/create the worker when the CPU goes down/up.
*
* Return:
* The pointer to the allocated worker on success, ERR_PTR(-ENOMEM)
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
kthread_worker-document-cpu-hotplug-handling.patch
mm-remove-the-unuseful-else-after-a-return-checkpatch-fixes.patch
mm-prevent-gup_fast-from-racing-with-cow-during-fork-checkpatch-fixes.patch
mm-swap_state-skip-meaningless-swap-cache-readahead-when-ra_infowin-==-0-fix.patch
mm-memcontrol-account-pagetables-per-node-fix.patch
mm-vmallocc-__vmalloc_area_node-avoid-32-bit-overflow.patch
mm-cma-improve-pr_debug-log-in-cma_release-fix.patch
mm.patch
mm-fix-initialization-of-struct-page-for-holes-in-memory-layout-checkpatch-fixes.patch
mm-vmstat-fix-proc-sys-vm-stat_refresh-generating-false-warnings-fix-2.patch
lib-cmdline_kunit-add-a-new-test-suite-for-cmdline-api-fix.patch
ilog2-improve-ilog2-for-constant-arguments-checkpatch-fixes.patch
lib-test_bitmapc-add-for_each_set_clump-test-cases-checkpatch-fixes.patch
checkpatch-fix-typo_spelling-check-for-words-with-apostrophe-fix.patch
resource-fix-kernel-doc-markups-checkpatch-fixes.patch
lib-ubsanc-mark-type_check_kinds-with-static-keyword-fix.patch
linux-next-rejects.patch
kmap-stupid-hacks-to-make-it-compile.patch
epoll-wire-up-syscall-epoll_pwait2-fix.patch
set_memory-allow-set_direct_map__noflush-for-multiple-pages-fix.patch
arch-mm-wire-up-memfd_secret-system-call-were-relevant-fix.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2020-12-15 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201215021145.ZDQFDjQbJ%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Qiang.Zhang@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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.