From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org, Olaf Hering <olaf@aepfle.de>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [Qemu-devel] [PATCH for-4.0 v3 0/2] roms: Avoid iPXE/EDK2 EFIROM variable clash, pass CFLAGS to EDK2 build tools
Date: Tue, 9 Apr 2019 15:45:34 +0200 [thread overview]
Message-ID: <20190409134536.15548-1-philmd@redhat.com> (raw)
Hi,
Two trivial fixes to avoid the latest EDK2 testing series to
cause trouble to downstream distributions (in particular if
they have PIE enforced).
Since v2:
- addressed Laszlo's suggestion
- reworded patch description
v2: https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01033.html
v1: https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01006.html
error report: https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg00992.html
Regards,
Phil.
Philippe Mathieu-Daudé (2):
roms: Rename the EFIROM variable to avoid clashing with iPXE
roms: Allow passing configure options to the EDK2 build tools
roms/Makefile | 23 ++++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
--
2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org, Olaf Hering <olaf@aepfle.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH for-4.0 v3 0/2] roms: Avoid iPXE/EDK2 EFIROM variable clash, pass CFLAGS to EDK2 build tools
Date: Tue, 9 Apr 2019 15:45:34 +0200 [thread overview]
Message-ID: <20190409134536.15548-1-philmd@redhat.com> (raw)
Message-ID: <20190409134534.wkrIZrEd-3QbhpjG_z1jxDXkUuffUBDK5T95DYnLmbI@z> (raw)
Hi,
Two trivial fixes to avoid the latest EDK2 testing series to
cause trouble to downstream distributions (in particular if
they have PIE enforced).
Since v2:
- addressed Laszlo's suggestion
- reworded patch description
v2: https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01033.html
v1: https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01006.html
error report: https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg00992.html
Regards,
Phil.
Philippe Mathieu-Daudé (2):
roms: Rename the EFIROM variable to avoid clashing with iPXE
roms: Allow passing configure options to the EDK2 build tools
roms/Makefile | 23 ++++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
--
2.20.1
next reply other threads:[~2019-04-09 13:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 13:45 Philippe Mathieu-Daudé [this message]
2019-04-09 13:45 ` [Qemu-devel] [PATCH for-4.0 v3 0/2] roms: Avoid iPXE/EDK2 EFIROM variable clash, pass CFLAGS to EDK2 build tools Philippe Mathieu-Daudé
2019-04-09 13:45 ` [Qemu-devel] [PATCH for-4.0 v3 1/2] roms: Rename the EFIROM variable to avoid clashing with iPXE Philippe Mathieu-Daudé
2019-04-09 13:45 ` Philippe Mathieu-Daudé
2019-04-09 15:19 ` Laszlo Ersek
2019-04-09 15:19 ` Laszlo Ersek
2019-04-09 13:45 ` [Qemu-devel] [PATCH for-4.0 v3 2/2] roms: Allow passing configure options to the EDK2 build tools Philippe Mathieu-Daudé
2019-04-09 13:45 ` Philippe Mathieu-Daudé
2019-04-09 14:58 ` Igor Mammedov
2019-04-09 14:58 ` Igor Mammedov
2019-04-09 15:24 ` Laszlo Ersek
2019-04-09 15:24 ` Laszlo Ersek
2019-04-09 14:00 ` [Qemu-devel] [PATCH for-4.0 v3 0/2] roms: Avoid iPXE/EDK2 EFIROM variable clash, pass CFLAGS to " Peter Maydell
2019-04-09 14:00 ` Peter Maydell
2019-04-09 15:25 ` Laszlo Ersek
2019-04-09 15:25 ` Laszlo Ersek
2019-04-09 15:27 ` Peter Maydell
2019-04-09 15:27 ` Peter Maydell
2019-04-09 15:05 ` Michael S. Tsirkin
2019-04-09 15:05 ` Michael S. Tsirkin
2019-04-09 15:11 ` Peter Maydell
2019-04-09 15:11 ` Peter Maydell
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-all 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=20190409134536.15548-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=olaf@aepfle.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).