public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ruiyu Ni <ruiyu.ni@intel.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [PATCH v2 0/6] Fix build failure due to tftp/dp library removal
Date: Tue, 28 Nov 2017 12:07:26 +0000	[thread overview]
Message-ID: <20171128120726.bvolgusyeq2pj5mj@bivouac.eciton.net> (raw)
In-Reply-To: <20171128120009.176316-1-ruiyu.ni@intel.com>

It would be helpful if the cover letter included a reference to the
commit that caused the breakage.

/
    Leif

On Tue, Nov 28, 2017 at 08:00:03PM +0800, Ruiyu Ni wrote:
> v2: v1 still causes build failures. I tried best to verify the build.
>     OVMF boot is also tried.
> 
> Ruiyu Ni (6):
>   ShellPkg/tftp: Correct file comments header of Tftp.uni
>   EmulatorPkg: Fix build failure due to Tftp library removal
>   ArmVirtPkg: Fix build failure due to Tftp library removal
>   BeagleBoardPkg: Fix build failure due to Tftp library removal
>   CorebootPayloadPkg: Fix build failure due to Tftp/Dp library removal
>   OvmfPkg: Add tftp dynamic command
> 
>  ArmVirtPkg/ArmVirt.dsc.inc                         | 11 ++++---
>  ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc               |  3 +-
>  ArmVirtPkg/ArmVirtXen.fdf                          |  3 +-
>  BeagleBoardPkg/BeagleBoardPkg.dsc                  | 17 +++++-----
>  BeagleBoardPkg/BeagleBoardPkg.fdf                  |  3 +-
>  CorebootPayloadPkg/CorebootPayloadPkg.fdf          |  4 ++-
>  CorebootPayloadPkg/CorebootPayloadPkgIa32.dsc      | 36 ++++++++++++----------
>  CorebootPayloadPkg/CorebootPayloadPkgIa32X64.dsc   | 36 ++++++++++++----------
>  EmulatorPkg/EmulatorPkg.dsc                        | 10 +++---
>  EmulatorPkg/EmulatorPkg.fdf                        |  3 +-
>  OvmfPkg/OvmfPkgIa32.dsc                            |  7 +++--
>  OvmfPkg/OvmfPkgIa32.fdf                            |  3 +-
>  OvmfPkg/OvmfPkgIa32X64.dsc                         |  7 +++--
>  OvmfPkg/OvmfPkgIa32X64.fdf                         |  3 +-
>  OvmfPkg/OvmfPkgX64.dsc                             |  7 +++--
>  OvmfPkg/OvmfPkgX64.fdf                             |  1 +
>  .../DynamicCommand/TftpDynamicCommand/Tftp.uni     |  4 +--
>  17 files changed, 93 insertions(+), 65 deletions(-)
> 
> -- 
> 2.15.0.gvfs.1.preview.4
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      parent reply	other threads:[~2017-11-28 12:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 12:00 [PATCH v2 0/6] Fix build failure due to tftp/dp library removal Ruiyu Ni
2017-11-28 12:00 ` [PATCH v2 1/6] ShellPkg/tftp: Correct file comments header of Tftp.uni Ruiyu Ni
2017-11-28 12:00 ` [PATCH v2 2/6] EmulatorPkg: Fix build failure due to Tftp library removal Ruiyu Ni
2017-11-28 12:00 ` [PATCH v2 3/6] ArmVirtPkg: " Ruiyu Ni
2017-11-28 12:00 ` [PATCH v2 4/6] BeagleBoardPkg: " Ruiyu Ni
2017-11-28 15:53   ` Ard Biesheuvel
2017-11-28 12:00 ` [PATCH v2 5/6] CorebootPayloadPkg: Fix build failure due to Tftp/Dp " Ruiyu Ni
2017-11-28 12:00 ` [PATCH v2 6/6] OvmfPkg: Add tftp dynamic command Ruiyu Ni
2017-11-28 12:07 ` Leif Lindholm [this message]

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=20171128120726.bvolgusyeq2pj5mj@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