From: Ruiyu Ni <ruiyu.ni@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH v4 0/3] Fix build failure due to tftp/dp library removal
Date: Wed, 29 Nov 2017 18:14:57 +0800 [thread overview]
Message-ID: <20171129101500.288384-1-ruiyu.ni@intel.com> (raw)
commit 0961002 and 92034c4 converted the tftp and dp from
NULL class library to dynamic command drivers.
Some platforms referencing the original tftp/dp NULL class
libraries need the platform DSC/FDF change to reference to the
new dynamic command drivers.
v4: Revise the commit message to mention the commit number which breaks
the build.
v3: Fix the patch issue in BeagleBordPkg change, which wrongly removed
UefiShellNetwork1CommandsLib.
Update OvmfPkg change to correct the copyright year and add more
commit message.
v2: v1 still causes build failures. I tried best to verify the build.
OVMF boot is also tried.
Ruiyu Ni (3):
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
ArmVirtPkg/ArmVirt.dsc.inc | 11 +++++++----
ArmVirtPkg/ArmVirtQemuFvMain.fdf.inc | 3 ++-
ArmVirtPkg/ArmVirtXen.fdf | 3 ++-
BeagleBoardPkg/BeagleBoardPkg.dsc | 16 +++++++++-------
BeagleBoardPkg/BeagleBoardPkg.fdf | 3 ++-
EmulatorPkg/EmulatorPkg.dsc | 10 ++++++----
EmulatorPkg/EmulatorPkg.fdf | 3 ++-
7 files changed, 30 insertions(+), 19 deletions(-)
--
2.15.0.gvfs.1.preview.4
next reply other threads:[~2017-11-29 10:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 10:14 Ruiyu Ni [this message]
2017-11-29 10:14 ` [PATCH v4 1/3] EmulatorPkg: Fix build failure due to Tftp library removal Ruiyu Ni
2017-11-29 10:14 ` [PATCH v4 2/3] ArmVirtPkg: " Ruiyu Ni
2017-11-29 13:53 ` Laszlo Ersek
2017-11-30 12:22 ` Laszlo Ersek
2017-11-30 13:16 ` Ard Biesheuvel
2017-12-01 1:48 ` Ni, Ruiyu
2017-12-01 10:12 ` Laszlo Ersek
2017-11-29 10:15 ` [PATCH v4 3/3] BeagleBoardPkg: " Ruiyu Ni
2017-11-29 11:30 ` Leif Lindholm
2017-11-30 12:22 ` Laszlo Ersek
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=20171129101500.288384-1-ruiyu.ni@intel.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