From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "H . Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-efi@vger.kernel.org, Ivan Hu <ivan.hu@canonical.com>,
Jeremy Kerr <jk@ozlabs.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] MAINTAINERS: Remove Matt Fleming as EFI co-maintainer
Date: Wed, 3 Jan 2018 12:43:04 +0000 [thread overview]
Message-ID: <20180103124304.GC3067@codeblueprint.co.uk> (raw)
In-Reply-To: <CAKv+Gu88QfuAQbLFbijHk9yG6TnYtkKPUYQfwpcQMX9z-cXcdQ@mail.gmail.com>
On Wed, 03 Jan, at 10:13:55AM, Ard Biesheuvel wrote:
> On 3 January 2018 at 09:44, Matt Fleming <matt@codeblueprint.co.uk> wrote:
> > Instate Ard Biesheuvel as the sole EFI maintainer and leave other folks
> > as maintainers for the EFI test driver and efivarfs file system.
> >
> > Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>
>
> Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> Thanks Matt
>
> > ---
> > MAINTAINERS | 5 +----
> > 1 file changed, 1 insertion(+), 4 deletions(-)
> >
> > Ard, if you want to add yourself as co-maintainer of the EFI test
> > driver or efivarfs, please go ahead. I'm sure no one would object.
> >
>
> I guess that makes sense. Should we just fold that in?
Sounds good to me.
next prev parent reply other threads:[~2018-01-03 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 9:44 [PATCH] MAINTAINERS: Remove Matt Fleming as EFI co-maintainer Matt Fleming
[not found] ` <20180103094417.6353-1-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2018-01-03 10:13 ` Ard Biesheuvel
2018-01-03 12:43 ` Matt Fleming [this message]
[not found] ` <20180103124304.GC3067-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2018-01-03 12:50 ` Ingo Molnar
2018-01-03 12:55 ` Ard Biesheuvel
[not found] ` <CAKv+Gu-Yv3J62jLsECodNJ2F2N2TFXpUbAkc8-O+FogoTYHTLw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-01-03 13:03 ` Ingo Molnar
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=20180103124304.GC3067@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=hpa@zytor.com \
--cc=ivan.hu@canonical.com \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=tglx@linutronix.de \
/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