From: Andrew Morton <akpm@linux-foundation.org>
To: "Zach O'Keefe" <zokeefe@google.com>
Cc: Yang Shi <shy828301@gmail.com>,
Saurabh Singh Sengar <ssengar@linux.microsoft.com>,
David Hildenbrand <david@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
Saurabh Singh Sengar <ssengar@microsoft.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [EXTERNAL] Re: [PATCH v3] mm/thp: fix "mm: thp: kill __transhuge_page_enabled()"
Date: Fri, 22 Sep 2023 10:20:16 -0700 [thread overview]
Message-ID: <20230922102016.95cab3640b17155a846874d9@linux-foundation.org> (raw)
In-Reply-To: <CAAa6QmTnx=kEijosNfq0DEPz4TeHFeOrgtwO0wfEeFUS5hgROw@mail.gmail.com>
On Fri, 22 Sep 2023 09:56:21 -0700 "Zach O'Keefe" <zokeefe@google.com> wrote:
> >From this back/forth with David/Matthew, seems like we're OK saying,
> "this was a mistake", and that we can take the patch (need some form
> of Ack or Reviewed-by from them first, to confirm)
Yup. And please let's update the changelog to reflect the details
which have been discussed thus far.
If the change *makes sense* for the current kernel then let's proceed,
regardless of the broken driver issue.
But adding a cc:stable would require extra argumentation, which I will
be interested to read ;)
prev parent reply other threads:[~2023-09-22 17:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 23:48 [PATCH v3] mm/thp: fix "mm: thp: kill __transhuge_page_enabled()" Zach O'Keefe
2023-08-22 5:20 ` [EXTERNAL] " Saurabh Singh Sengar
2023-08-24 7:39 ` David Hildenbrand
2023-08-24 13:59 ` Zach O'Keefe
2023-08-24 14:05 ` David Hildenbrand
2023-08-24 14:47 ` Zach O'Keefe
2023-08-24 15:39 ` [EXTERNAL] " Saurabh Singh Sengar
2023-08-25 7:59 ` David Hildenbrand
2023-08-25 12:49 ` Matthew Wilcox
2023-08-25 12:58 ` David Hildenbrand
2023-08-25 15:09 ` Zach O'Keefe
2023-09-06 6:58 ` Saurabh Singh Sengar
2023-09-20 5:44 ` Saurabh Singh Sengar
2023-09-22 16:54 ` Yang Shi
2023-09-22 16:56 ` Zach O'Keefe
2023-09-22 17:20 ` Andrew Morton [this message]
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=20230922102016.95cab3640b17155a846874d9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@microsoft.com \
--cc=willy@infradead.org \
--cc=zokeefe@google.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 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).