From: Laszlo Ersek <lersek@redhat.com>
To: edk2-devel-01 <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jiaxin Wu <jiaxin.wu@intel.com>,
Jordan Justen <jordan.l.justen@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: [PATCH v2 0/2] OvmfPkg: refresh -D E1000_ENABLE (Intel proprietary driver for e1000)
Date: Tue, 4 Jul 2017 12:00:20 +0200 [thread overview]
Message-ID: <20170704100022.18828-1-lersek@redhat.com> (raw)
Version 2 of the series previously posted at
<https://lists.01.org/pipermail/edk2-devel/2017-June/011964.html>.
In this version, LMFA references in the commit message of patch #1 have
been replaced with Liming's explanation from the mailing list. Patch #2
has been marked with Jiaxin's feedback tags. No code changes in either
patch.
Repo: https://github.com/lersek/edk2.git
Branch: e1000_refresh_v2
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Jiaxin Wu <jiaxin.wu@intel.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Thanks,
Laszlo
Laszlo Ersek (2):
OvmfPkg: disable build-time relocation for DXEFV modules
OvmfPkg: update -D E1000_ENABLE from Intel PROEFI v.07 to BootUtil
v.22
OvmfPkg/OvmfPkgIa32.fdf | 6 +---
OvmfPkg/OvmfPkgIa32X64.fdf | 3 +-
OvmfPkg/OvmfPkgX64.fdf | 3 +-
OvmfPkg/README | 31 +++++++++++++-------
4 files changed, 26 insertions(+), 17 deletions(-)
--
2.13.1.3.g8be5a757fa67
next reply other threads:[~2017-07-04 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 10:00 Laszlo Ersek [this message]
2017-07-04 10:00 ` [PATCH v2 1/2] OvmfPkg: disable build-time relocation for DXEFV modules Laszlo Ersek
2017-07-04 11:54 ` Gao, Liming
2017-07-04 20:02 ` Laszlo Ersek
2017-07-04 10:00 ` [PATCH v2 2/2] OvmfPkg: update -D E1000_ENABLE from Intel PROEFI v.07 to BootUtil v.22 Laszlo Ersek
2017-07-05 20:14 ` [PATCH v2 0/2] OvmfPkg: refresh -D E1000_ENABLE (Intel proprietary driver for e1000) 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=20170704100022.18828-1-lersek@redhat.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