public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "James Bottomley" <jejb@linux.ibm.com>
To: Laszlo Ersek <lersek@redhat.com>,
	Ard Biesheuvel <ard.biesheuvel@arm.com>,
	Sean Brogan <spbrogan@outlook.com>,
	devel@edk2.groups.io
Cc: "Jordan Justen" <jordan.l.justen@intel.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	"Leif Lindholm (Nuvia address)" <leif@nuviainc.com>
Subject: Re: [edk2-devel] [PATCH 1/2] OvmfPkg: start using the ECC plugin exception list
Date: Mon, 07 Dec 2020 18:10:12 -0800	[thread overview]
Message-ID: <ee2b36018eda21d37a7efcdcdc92b77cf46ab1ea.camel@linux.ibm.com> (raw)
In-Reply-To: <3b931320-5afb-0dae-e8d2-f2e56be88177@redhat.com>

On Tue, 2020-12-08 at 02:56 +0100, Laszlo Ersek wrote:
> On 12/04/20 17:05, Ard Biesheuvel wrote:
[...]
> > Could we perhaps use a special tag? Or simply overrule ECC if the
> > patch in question has a Reviewed-by from the maintainer (*not* from
> > a reviewer) of the package in question?
> > 
> > As for the 'risky' - I agree that it is likely to misunderstood, so
> > better find a different word to describe this.
> > 
> 
> Yeah, let me drop this one patch and see if we can disable ECC
> globally, or implement a github label to disable it.
> 
> James, is it OK if we delay merging of your v3 series a bit?

Sure, there's nothing tremendously urgent.  I'm about to post the qemu
enabling patch, but as long as the GUIDs don't change (or the format of
the reset block) a delay shouldn't matter.

James



  reply	other threads:[~2020-12-08  2:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  3:21 [PATCH 0/2] OvmfPkg: CI tweaks Laszlo Ersek
2020-12-04  3:21 ` [PATCH 1/2] OvmfPkg: start using the ECC plugin exception list Laszlo Ersek
2020-12-04  4:05   ` [edk2-devel] " Sean
2020-12-04 15:22     ` Laszlo Ersek
2020-12-04 15:36       ` Laszlo Ersek
2020-12-04 16:05         ` Ard Biesheuvel
2020-12-08  1:56           ` Laszlo Ersek
2020-12-08  2:10             ` James Bottomley [this message]
2020-12-08  7:05             ` Ard Biesheuvel
2020-12-08 18:45             ` Sean
2020-12-10  8:23               ` Laszlo Ersek
2020-12-04 18:28         ` Sean
2020-12-08  1:46           ` Laszlo Ersek
2020-12-04  3:21 ` [PATCH 2/2] OvmfPkg: add "gGrubFileGuid=Grub" to GuidCheck.IgnoreDuplicates Laszlo Ersek
2020-12-04 12:42   ` Philippe Mathieu-Daudé

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-list 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=ee2b36018eda21d37a7efcdcdc92b77cf46ab1ea.camel@linux.ibm.com \
    --to=devel@edk2.groups.io \
    /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