From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, wangkefeng.wang@huawei.com,
rppt@kernel.org, jwilk@jwilk.net, akpm@linux-foundation.org
Subject: [merged mm-stable] mm-fix-typo-in-__vm_enough_memory-warning.patch removed from -mm tree
Date: Mon, 13 Feb 2023 15:55:41 -0800 [thread overview]
Message-ID: <20230213235541.CE802C433EF@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: fix typo in __vm_enough_memory warning
has been removed from the -mm tree. Its filename was
mm-fix-typo-in-__vm_enough_memory-warning.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Jakub Wilk <jwilk@jwilk.net>
Subject: mm: fix typo in __vm_enough_memory warning
Date: Fri, 10 Feb 2023 21:33:16 +0100
Link: https://lkml.kernel.org/r/20230210203316.5613-1-jwilk@jwilk.net
Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
Acked-by: Mike Rapoport (IBM) <rppt@kernel.org>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/mm/util.c~mm-fix-typo-in-__vm_enough_memory-warning
+++ a/mm/util.c
@@ -967,7 +967,7 @@ int __vm_enough_memory(struct mm_struct
if (percpu_counter_read_positive(&vm_committed_as) < allowed)
return 0;
error:
- pr_warn_ratelimited("%s: pid: %d, comm: %s, no enough memory for the allocation\n",
+ pr_warn_ratelimited("%s: pid: %d, comm: %s, not enough memory for the allocation\n",
__func__, current->pid, current->comm);
vm_unacct_memory(pages);
_
Patches currently in -mm which might be from jwilk@jwilk.net are
reply other threads:[~2023-02-13 23:56 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=20230213235541.CE802C433EF@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=jwilk@jwilk.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=wangkefeng.wang@huawei.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.