From: Lukas Wunner <lukas@wunner.de>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: EFI co-maintainer
Date: Wed, 21 Sep 2016 19:59:51 +0200 [thread overview]
Message-ID: <20160921175951.GA3387@wunner.de> (raw)
In-Reply-To: <20160921150912.GM2892@codeblueprint.co.uk>
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
next prev parent reply other threads:[~2016-09-21 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 15:09 EFI co-maintainer Matt Fleming
2016-09-21 15:12 ` Grant Likely
2016-09-21 17:59 ` Lukas Wunner [this message]
2016-09-22 8:34 ` Matt Fleming
2016-09-22 8:49 ` Ard Biesheuvel
2016-09-22 8:57 ` Lukas Wunner
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=20160921175951.GA3387@wunner.de \
--to=lukas@wunner.de \
--cc=ard.biesheuvel@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).