public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: edk2-devel@lists.01.org, graeme.gregory@linaro.org
Subject: Re: [PATCH edk2-platforms 0/2] enable FPDT table for SynQuacer
Date: Thu, 31 May 2018 22:16:08 +0100	[thread overview]
Message-ID: <20180531211608.jqwwtfv4s5e3p2ft@bivouac.eciton.net> (raw)
In-Reply-To: <20180531104634.23215-1-ard.biesheuvel@linaro.org>

On Thu, May 31, 2018 at 12:46:32PM +0200, Ard Biesheuvel wrote:
> Enable some of the status code reporting infrastructure in patch #1 so
> we can include the FPDT DXE driver in patch #2 which produces the FPDT
> diagnostic table which tells us how much time was spent in the firmware,
> in the OS loader, and in ExitBootServices().
> 
> Ard Biesheuvel (2):
>   Platform/DeveloperBox: wire up status code reporting for DXE phase
>   Platform/DeveloperBox: enable FPDT table

For the series:
Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>

>  Platform/Socionext/DeveloperBox/DeveloperBox.dsc | 12 ++++++++++++
>  Platform/Socionext/DeveloperBox/DeveloperBox.fdf |  2 ++
>  Silicon/Socionext/SynQuacer/Acpi.dsc.inc         |  6 ++++++
>  3 files changed, 20 insertions(+)
> 
> -- 
> 2.17.0
> 


  parent reply	other threads:[~2018-05-31 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 10:46 [PATCH edk2-platforms 0/2] enable FPDT table for SynQuacer Ard Biesheuvel
2018-05-31 10:46 ` [PATCH edk2-platforms 1/2] Platform/DeveloperBox: wire up status code reporting for DXE phase Ard Biesheuvel
2018-05-31 10:46 ` [PATCH edk2-platforms 2/2] Platform/DeveloperBox: enable FPDT table Ard Biesheuvel
2018-05-31 21:16 ` Leif Lindholm [this message]
2018-06-01 10:18   ` [PATCH edk2-platforms 0/2] enable FPDT table for SynQuacer Leif Lindholm

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=20180531211608.jqwwtfv4s5e3p2ft@bivouac.eciton.net \
    --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