From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, riel@surriel.com, mhocko@suse.com,
lnyng@fb.com, hannes@cmpxchg.org, guro@fb.com,
chris@chrisdown.name, akpm@linux-foundation.org
Subject: [folded-merged] mm-memcontrol-fix-occasional-ooms-due-to-proportional-memorylow-reclaim-checkpatch-fixes.patch removed from -mm tree
Date: Thu, 19 Aug 2021 18:55:37 -0700 [thread overview]
Message-ID: <20210820015537.o6ime%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm-memcontrol-fix-occasional-ooms-due-to-proportional-memorylow-reclaim-checkpatch-fixes
has been removed from the -mm tree. Its filename was
mm-memcontrol-fix-occasional-ooms-due-to-proportional-memorylow-reclaim-checkpatch-fixes.patch
This patch was dropped because it was folded into mm-memcontrol-fix-occasional-ooms-due-to-proportional-memorylow-reclaim.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-memcontrol-fix-occasional-ooms-due-to-proportional-memorylow-reclaim-checkpatch-fixes
WARNING: Possible repeated word: 'back'
#104: FILE: mm/vmscan.c:107:
+ * result, then go back back for one more cycle that reclaims
total: 0 errors, 1 warnings, 100 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
./patches/mm-memcontrol-fix-occasional-ooms-due-to-proportional-memorylow-reclaim.patch has style problems, please review.
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
Please run checkpatch prior to sending patches
Cc: Chris Down <chris@chrisdown.name>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Leon Yang <lnyng@fb.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Rik van Riel <riel@surriel.com>
Cc: Roman Gushchin <guro@fb.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/vmscan.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/vmscan.c~mm-memcontrol-fix-occasional-ooms-due-to-proportional-memorylow-reclaim-checkpatch-fixes
+++ a/mm/vmscan.c
@@ -104,8 +104,8 @@ struct scan_control {
* don't threaten to OOM. If any cgroup is reclaimed at
* reduced force or passed over entirely due to its memory.low
* setting (memcg_low_skipped), and nothing is reclaimed as a
- * result, then go back back for one more cycle that reclaims
- * the protected memory (memcg_low_reclaim) to avert OOM.
+ * result, then go back for one more cycle that reclaims the protected
+ * memory (memcg_low_reclaim) to avert OOM.
*/
unsigned int memcg_low_reclaim:1;
unsigned int memcg_low_skipped:1;
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-memcontrol-fix-occasional-ooms-due-to-proportional-memorylow-reclaim.patch
mm.patch
mm-gup-fix-potential-pgmap-refcnt-leak-in-__gup_device_huge-fix.patch
mm-gup-fix-potential-pgmap-refcnt-leak-in-__gup_device_huge-fix-fix.patch
lazy-tlb-allow-lazy-tlb-mm-refcounting-to-be-configurable-fix.patch
mm-compaction-optimize-proactive-compaction-deferrals-fix.patch
mm-compaction-support-triggering-of-proactive-compaction-by-user-fix.patch
mm-mempolicy-convert-from-atomic_t-to-refcount_t-on-mempolicy-refcnt-fix.patch
mm-idle_page_tracking-make-pg_idle-reusable-fix-fix.patch
mm-damon-implement-primitives-for-the-virtual-memory-address-spaces-fix.patch
mm-damon-implement-a-debugfs-based-user-space-interface-fix.patch
mm-damon-implement-a-debugfs-based-user-space-interface-fix-fix.patch
fs-epoll-use-a-per-cpu-counter-for-users-watches-count-fix-fix.patch
log-if-a-core-dump-is-aborted-due-to-changed-file-permissions-fix.patch
linux-next-rejects.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2021-08-20 1:55 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=20210820015537.o6ime%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chris@chrisdown.name \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lnyng@fb.com \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=riel@surriel.com \
/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.