linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	John Hubbard <jhubbard@nvidia.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Gerald Schaefer <gerald.schaefer@de.ibm.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH v4 00/26] mm: Page fault accounting cleanups
Date: Tue, 30 Jun 2020 19:35:02 -0400	[thread overview]
Message-ID: <20200630233502.GC40675@xz-x1> (raw)
In-Reply-To: <20200630160548.fc8d1f93148e74e544850bf3@linux-foundation.org>

On Tue, Jun 30, 2020 at 04:05:48PM -0700, Andrew Morton wrote:
> On Tue, 30 Jun 2020 17:11:55 -0400 Peter Xu <peterx@redhat.com> wrote:
> 
> > On Tue, Jun 30, 2020 at 04:45:01PM -0400, Peter Xu wrote:
> > > v4:
> > > - rebase to linux-next/akpm
> > > - picked one more r-b
> > 
> > I fixed some stuff in the send scripts but definitely broke something else on
> > the chaining of the messages.  Andrew, please let me know if you want me to
> > resend...  Sorry for that.
> 
> Well, the words
> 
> : Since v2 changed quite a lot from v1, changelog is omitted, and I also
> : didn't have a chance to pick up any r-b in previous version.  I really
> : appreciate anyone who has looked at v1.  V1 for reference:
> 
> make me think "not yet".  But this patchset is v4, so all confused.

I posted v2 & v3 with incorrect versioning, so they were all shown as v1 in the
subjects.  I fixed it in v4 so it seemed to have jumped from v1->v4.  Sorry for
the confusion.

Regarding to the cover letter: I rewrote the cover letter in v2 because it
changed a lot.  While v3 & v4 changed little, so I kept the v2 cover letter
then appended with changelogs for v3/v4 at the top because the content of the
v2 cover letter still stand.

> 
> I'm thinking we give this v4 a week for people to check it over, gather
> up the revews and acks, incorporate the change suggested by David, redo
> and double-check the cover letter then shoot for a v5?

Will do.  Thanks,

-- 
Peter Xu



      reply	other threads:[~2020-06-30 23:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 20:45 Peter Xu
2020-06-30 21:11 ` Peter Xu
2020-06-30 23:05   ` Andrew Morton
2020-06-30 23:35     ` 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=20200630233502.GC40675@xz-x1 \
    --to=peterx@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=gerald.schaefer@de.ibm.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mpe@ellerman.id.au \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.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