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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 13 Jan 2021 07:57:26 +1100
From:   Stephen Rothwell <>
To:     Daniel Vetter <>
Cc:     DRI Development <>,
        LKML <>,,,
        Daniel Vetter <>,,,
Subject: Re: [PATCH v7 00/17] follow_pfn and other iomap races

Hi Daniel,

On Tue, 12 Jan 2021 14:24:27 +0100 Daniel Vetter <> wrote:
> As Jason suggested, I've pulled the first 1 patches into a topic branch.
> Stephen, can you please add the below to linux-next for the 5.12 merge
> window?
> git:// topic/iomem-mmap-vs-gup

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
     * submitted under GPL v2 (or later) and include the Contributor's
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

Stephen Rothwell

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists