linux-kernel - Re: EFI co-maintainer

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:   Wed, 21 Sep 2016 19:59:51 +0200
From:   Lukas Wunner <lukas@...ner.de>
To:     Matt Fleming <matt@...eblueprint.co.uk>
Cc:     linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Ard Biesheuvel <ard.biesheuvel@...aro.org>
Subject: Re: EFI co-maintainer

Hi Matt, Hi Ard,

On Wed, Sep 21, 2016 at 04:09:12PM +0100, Matt Fleming wrote:
> I've asked, and Ard has agreed to step up and help me co-maintain the
> EFI subsystem.
> 
> Given that there are now two maintainers, we're moving to a shared git
> repository on kernel.org, hosted at,
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git
> 
> Expect a MAINTAINERS patch soon.
> 
> I do plan on keeping the existing tree in sync for the time being, so
> it won't actually matter which repository people base their patches
> on. Hopefully the disruption to patch submitters will be minimal.
> 
> Thanks again Ard!

That is great to hear, thanks a lot from me as well.

Just curious, are there any plans to integrate the new repo into
linux-next?  It would be great to have testing as early as possible.

Also, if this isn't too much trouble, would it be possible to merge
urgent into next when patches are added in the future?  When I tested
my patches during this release cycle, I tried to pull in everything
from efi/urgent + efi/next into my development branch but hit some
non-trivial merge conflicts in portions of the EFI code I wasn't
familiar with.  And ISTR that efi/next was based on 4.7, not 4.8-rc.
In the end I just rebased my patches on efi/next, but felt a bit uneasy
as I wasn't testing what the code would eventually look like.

Thanks again,

Lukas