From: Ard Biesheuvel <ardb@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-efi <linux-efi@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arvind Sankar <nivedita@alum.mit.edu>,
Benjamin Thiel <b.thiel@posteo.de>,
Dave Young <dyoung@redhat.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Javier Martinez Canillas <javierm@redhat.com>,
Jerry Snitselaar <jsnitsel@redhat.com>,
Lenny Szubowicz <lszubowi@redhat.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Loic Yhuel <loic.yhuel@gmail.com>,
Matthew Garrett <mjg59@google.com>,
Mike Lothian <mike@fireburn.co.uk>,
Punit Agrawal <punit1.agrawal@toshiba.co.jp>
Subject: Re: [GIT PULL 0/7] EFI fixes for v5.7
Date: Fri, 22 May 2020 15:44:21 +0200 [thread overview]
Message-ID: <CAMj1kXHogO=3wAyZPi9WtHP9++N5KH6OjNgY_CQ_o8nZJ5jjVA@mail.gmail.com> (raw)
In-Reply-To: <20200522134004.GF28750@zn.tnic>
On Fri, 22 May 2020 at 15:40, Borislav Petkov <bp@alien8.de> wrote:
>
> On Fri, May 22, 2020 at 03:06:20PM +0200, Ard Biesheuvel wrote:
> > Ping?
>
> Did you want to make your tags unique from the next pull request onwards
> and I were supposed to pull this one as is?
>
What usually happens is that Ingo applies the patches piecemeal,
ignoring the tag altogether, so without any coordination between you
as x86 maintainers or communication back to me, that is what i was
expecting to happen this time as well.
Note that I have another PR pending since two weeks ago [0].
So if you want to start dealing with the EFI trees in a different way
from now on, that is perfectly fine with me, but please align with
Ingo and Thomas first.
Thanks,
Ard.
[0] https://lore.kernel.org/linux-efi/20200508180157.1816-1-ardb@kernel.org/
next prev parent reply other threads:[~2020-05-22 13:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 12:57 [GIT PULL 0/7] EFI fixes for v5.7 Ard Biesheuvel
2020-05-17 12:57 ` [PATCH 1/7] efi/libstub: Avoid returning uninitialized data from setup_graphics() Ard Biesheuvel
2020-05-17 12:57 ` [PATCH 2/7] efi/earlycon: Fix early printk for wider fonts Ard Biesheuvel
2020-05-17 12:57 ` [PATCH 3/7] efi/libstub/x86: Avoid EFI map buffer alloc in allocate_e820() Ard Biesheuvel
2020-05-17 12:57 ` [PATCH 4/7] efi: cper: Add support for printing Firmware Error Record Reference Ard Biesheuvel
2020-05-17 12:57 ` [PATCH 5/7] x86/boot: Mark global variables as static Ard Biesheuvel
2020-05-17 12:57 ` [PATCH 6/7] efi: Pull up arch-specific prototype efi_systab_show_arch() Ard Biesheuvel
2020-05-17 12:57 ` [PATCH 7/7] tpm: check event log version before reading final events Ard Biesheuvel
2020-05-18 9:07 ` [GIT PULL 0/7] EFI fixes for v5.7 Borislav Petkov
2020-05-18 9:15 ` Ard Biesheuvel
2020-05-22 13:06 ` Ard Biesheuvel
2020-05-22 13:40 ` Borislav Petkov
2020-05-22 13:44 ` Ard Biesheuvel [this message]
2020-05-22 14:04 ` Thomas Gleixner
2020-05-22 14:45 ` Ard Biesheuvel
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='CAMj1kXHogO=3wAyZPi9WtHP9++N5KH6OjNgY_CQ_o8nZJ5jjVA@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=b.thiel@posteo.de \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=javierm@redhat.com \
--cc=jsnitsel@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.yhuel@gmail.com \
--cc=lszubowi@redhat.com \
--cc=mike@fireburn.co.uk \
--cc=mingo@kernel.org \
--cc=mjg59@google.com \
--cc=nivedita@alum.mit.edu \
--cc=punit1.agrawal@toshiba.co.jp \
--cc=tglx@linutronix.de \
--cc=xypron.glpk@gmx.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;
as well as URLs for NNTP newsgroup(s).