linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Yang Shi <shy828301@gmail.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Jann Horn <jannh@google.com>,
	Matthew Wilcox <willy@infradead.org>,
	Linux MM <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>
Subject: Re: [v2 PATCH] fs/proc: task_mmu.c: don't read mapcount for migration entry
Date: Tue, 25 Jan 2022 18:08:32 -0800	[thread overview]
Message-ID: <20220125180832.8d12103399c82dd652b56577@linux-foundation.org> (raw)
In-Reply-To: <CAHbLzkoY36htvh-+0qtFUM1yF2Jnq-wzXdHJJ82x28q=HK5njw@mail.gmail.com>

On Tue, 25 Jan 2022 17:59:48 -0800 Yang Shi <shy828301@gmail.com> wrote:

> The proper fixes tag should be:
> Fixes: e9b61f19858a ("thp: reintroduce split_huge_page()").
> 
> Andrew, could you please update this in -mm tree? Thanks.

Done, thanks.


  reply	other threads:[~2022-01-26  2:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20 20:28 [v2 PATCH] fs/proc: task_mmu.c: don't read mapcount for migration entry Yang Shi
2022-01-26  1:59 ` Yang Shi
2022-01-26  2:08   ` Andrew Morton [this message]
2022-01-26 10:51 ` David Hildenbrand
2022-01-26 11:29   ` Jann Horn
2022-01-26 11:38     ` David Hildenbrand
2022-01-26 11:48       ` Jann Horn
2022-01-26 11:57         ` David Hildenbrand
2022-01-26 16:53           ` Yang Shi
2022-01-26 16:58             ` David Hildenbrand
2022-01-26 18:43               ` Yang Shi
2022-01-26 18:54                 ` David Hildenbrand
2022-01-27 19:42                   ` Yang Shi
2022-01-27 21:16                   ` Yang Shi
2022-01-28  8:02                     ` David Hildenbrand
2022-01-28 16:53                       ` Yang Shi
2022-01-27 20:51     ` Yang Shi

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=20220125180832.8d12103399c82dd652b56577@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.com \
    --cc=stable@vger.kernel.org \
    --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).