linux-kernel - Re: [GIT PULL 00/13] First batch of EFI updates for v4.13

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 5 Jun 2017 17:53:15 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Ard Biesheuvel <ard.biesheuvel@...aro.org>
Cc:     "linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        "H . Peter Anvin" <hpa@...or.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Matt Fleming <matt@...eblueprint.co.uk>,
        Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com>
Subject: Re: [GIT PULL 00/13] First batch of EFI updates for v4.13


* Ard Biesheuvel <ard.biesheuvel@...aro.org> wrote:

> > It would be nice to fix your SOB flow: the maintainer who queues up a patch should
> > add the SOB, and add an Acked-by of the co-maintainer if the co-maintainer agrees
> > with the patch as well. The tree should typically not be rebased after that point
> > (especially not by the other co-maintainer) - that's just indicative of a messy
> > workflow.
> 
> OK, so this is exactly what we have in the queue right now, and what I
> sent the pull request for.

Ok, the SOB chains are perfect - and I've started applying the patches to 
tip:efi/core.

Most of them are looking good, except #1 which won't apply. There were a few small 
details in changelogs that I have fixed up in place.

Will push out the rest if they pass testing.

Thanks,

	Ingo