On 10/02/18 14:17, [email protected] wrote: > From: Marc-André Lureau <[email protected]> > > This is for conformance with the TCG "Platform Reset Attack Mitigation > Specification". Because clearing the CPU caches at boot doesn't impact > performance significantly, do it unconditionally, for simplicity's > sake. > > Flush the cache on all logical processors, thanks to > EFI_PEI_MP_SERVICES_PPI and CacheMaintenanceLib. > > Cc: Jordan Justen <[email protected]> > Cc: Laszlo Ersek <[email protected]> > Cc: Ard Biesheuvel <[email protected]> > Cc: Anthony Perard <[email protected]> > Cc: Julien Grall <[email protected]> > Contributed-under: TianoCore Contribution Agreement 1.1 > Signed-off-by: Marc-André Lureau <[email protected]> > Message-Id: <[email protected]> > --- > > v3: > - update top comment with notes about TCG spec > - sort headers inclusion
So, meta comments first... I got this patch (v3) in three variants: (a) the one you sent me off-list, as quoted-printable: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable (b) this message, reaching me directly from you: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit (c) this message, reflected by the edk2-devel list software, from you to me: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Results: - git-am fails with (a). - git-am *also* fails with (c). - git-am only works on (b). Which means that your setup is now correct, but some mail server on path (c) is broken, and corrupts your patch email when it transcodes the email to base64. Yay! I guess I'll work with copy (b), in my inbox. Sigh, is the mailing list workflow actually *more* broken than github pull requests? I thought that was impossible, but I guess I'm being proven wrong. Laszlo _______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
