From: Peter Xu <peterx@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, shy828301@gmail.com,
mike.kravetz@oracle.com, kirill@shutemov.name, hughd@google.com,
david@redhat.com
Subject: Re: + mm-wire-up-tail-page-poisoning-over-mappings.patch added to mm-unstable branch
Date: Sun, 20 Aug 2023 21:10:20 -0400 [thread overview]
Message-ID: <ZOK5fCHC2K+c7a1d@x1n> (raw)
In-Reply-To: <ZN/tgtMhuSFDFD6a@casper.infradead.org>
On Fri, Aug 18, 2023 at 11:15:30PM +0100, Matthew Wilcox wrote:
> On Fri, Aug 18, 2023 at 02:02:14PM -0700, Andrew Morton wrote:
> > On Fri, 18 Aug 2023 21:29:50 +0100 Matthew Wilcox <willy@infradead.org> wrote:
> >
> > > On Fri, Aug 18, 2023 at 01:00:30PM -0700, Andrew Morton wrote:
> > > > From: Peter Xu <peterx@redhat.com>
> > > > Subject: mm: wire up tail page poisoning over ->mappings
> > > > Date: Tue, 15 Aug 2023 17:06:59 -0400
> > >
> > > Did I need to keep NAKing this patch, or did you disagree with my NAK?
> >
> > This is the first time this patch has been sent out (under this title)
> > and it sat on the lists unreplied-to for three days.
>
> He didn't address my objection to the earlier one.
>
> https://lore.kernel.org/linux-mm/ZNp7yUgUrIpILnXu@casper.infradead.org/
I replied.
https://lore.kernel.org/linux-mm/ZNqFv0AwkfDKExiw@x1n/
>
> Anyway, I've replied to it now in *that* thread.
This patch should be straightforward to me, I really don't understand your
point.
I can reply to you again there, of course. Let me try.
--
Peter Xu
prev parent reply other threads:[~2023-08-21 1:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 20:00 + mm-wire-up-tail-page-poisoning-over-mappings.patch added to mm-unstable branch Andrew Morton
2023-08-18 20:29 ` Matthew Wilcox
2023-08-18 21:02 ` Andrew Morton
2023-08-18 22:15 ` Matthew Wilcox
2023-08-21 1:10 ` Peter Xu [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=ZOK5fCHC2K+c7a1d@x1n \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mm-commits@vger.kernel.org \
--cc=shy828301@gmail.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 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.