linux-kernel - Re: [PATCH v4 00/26] mm: Page fault accounting cleanups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20200630233502.GC40675@xz-x1>
Date:   Tue, 30 Jun 2020 19:35:02 -0400
From:   Peter Xu <peterx@...hat.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org,
        John Hubbard <jhubbard@...dia.com>,
        Michael Ellerman <mpe@...erman.id.au>,
        Gerald Schaefer <gerald.schaefer@...ibm.com>,
        Andrea Arcangeli <aarcange@...hat.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Will Deacon <will@...nel.org>
Subject: Re: [PATCH v4 00/26] mm: Page fault accounting cleanups

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@...hat.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