From: Shuah Khan <skhan@linuxfoundation.org>
To: Suren Baghdasaryan <surenb@google.com>, akpm@linux-foundation.org
Cc: mhocko@suse.com, rientjes@google.com, willy@infradead.org,
hannes@cmpxchg.org, guro@fb.com, minchan@kernel.org,
kirill@shutemov.name, aarcange@redhat.com, brauner@kernel.org,
hch@infradead.org, oleg@redhat.com, david@redhat.com,
jannh@google.com, shakeelb@google.com, peterx@redhat.com,
jhubbard@nvidia.com, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel-team@android.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 2/2] mm: delete unused MMF_OOM_VICTIM flag
Date: Mon, 16 May 2022 21:13:05 -0600 [thread overview]
Message-ID: <fae23c69-18fa-a86f-f35a-e3c4d646a53c@linuxfoundation.org> (raw)
In-Reply-To: <20220516075619.1277152-2-surenb@google.com>
On 5/16/22 1:56 AM, Suren Baghdasaryan wrote:
> With the last usage of MMF_OOM_VICTIM in exit_mmap gone, this flag is
> now unused and can be removed.
>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> include/linux/oom.h | 9 ---------
> include/linux/sched/coredump.h | 7 +++----
> mm/oom_kill.c | 4 +---
> 3 files changed, 4 insertions(+), 16 deletions(-)
>
Looks good to me.
Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
next prev parent reply other threads:[~2022-05-17 3:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 7:56 [PATCH v2 1/2] mm: drop oom code from exit_mmap Suren Baghdasaryan
2022-05-16 7:56 ` [PATCH v2 2/2] mm: delete unused MMF_OOM_VICTIM flag Suren Baghdasaryan
2022-05-17 3:13 ` Shuah Khan [this message]
2022-05-17 3:12 ` [PATCH v2 1/2] mm: drop oom code from exit_mmap Shuah Khan
2022-05-19 19:29 ` Andrew Morton
2022-05-19 20:33 ` Liam Howlett
2022-05-19 21:43 ` Suren Baghdasaryan
2022-05-19 22:34 ` Liam Howlett
2022-05-19 20:22 ` Liam Howlett
2022-05-19 21:33 ` Suren Baghdasaryan
2022-05-19 22:14 ` Suren Baghdasaryan
2022-05-19 22:56 ` Liam Howlett
2022-05-19 23:08 ` Suren Baghdasaryan
2022-05-20 7:21 ` Michal Hocko
2022-05-20 15:55 ` Suren Baghdasaryan
2022-05-20 16:17 ` Suren Baghdasaryan
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=fae23c69-18fa-a86f-f35a-e3c4d646a53c@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=jannh@google.com \
--cc=jhubbard@nvidia.com \
--cc=kernel-team@android.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=oleg@redhat.com \
--cc=peterx@redhat.com \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=willy@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;
as well as URLs for NNTP newsgroup(s).