From: Laszlo Ersek <lersek@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/2] roms: Add 'clean' make rule and EDK2 documentation fix
Date: Tue, 7 May 2019 12:56:24 +0200 [thread overview]
Message-ID: <fcf6d003-36b2-9e8c-4708-58293a610a6e@redhat.com> (raw)
In-Reply-To: <20190506141923.12183-1-philmd@redhat.com>
On 05/06/19 16:19, Philippe Mathieu-Daudé wrote:
> Hi,
>
> Two trivial patches waiting Laszlo's series to land.
... I think you can submit a pullreq with these two patches now --
because I believe that you refer to
[Qemu-devel] [PULL 00/12] bundle edk2 platform firmware with QEMU
above, and that's been merged for a while now.
Thanks!
Laszlo
> Since v2:
> - removed duplicated space chars (Laszlo)
> - added Laszlo's R-b tag
>
> Since v1:
> - rebased
>
> v2:
> https://lists.gnu.org/archive/html/qemu-devel/2019-05/msg00853.html
> v1:
> https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01589.html
> https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg01598.html
>
> Philippe Mathieu-Daudé (2):
> roms: Correct the EDK2_BASETOOLS_OPTFLAGS variable description
> roms: List and describe the Makefile 'clean' rule
>
> roms/Makefile | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2019-05-07 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 14:19 [Qemu-devel] [PATCH v3 0/2] roms: Add 'clean' make rule and EDK2 documentation fix Philippe Mathieu-Daudé
2019-05-06 14:19 ` [Qemu-devel] [PATCH v3 1/2] roms: Correct the EDK2_BASETOOLS_OPTFLAGS variable description Philippe Mathieu-Daudé
2019-05-22 13:39 ` Laurent Vivier
2019-05-06 14:19 ` [Qemu-devel] [PATCH v3 2/2] roms: List and describe the Makefile 'clean' rule Philippe Mathieu-Daudé
2019-05-22 13:40 ` Laurent Vivier
2019-05-07 10:56 ` Laszlo Ersek [this message]
2019-05-07 12:17 ` [Qemu-devel] [PATCH v3 0/2] roms: Add 'clean' make rule and EDK2 documentation fix Philippe Mathieu-Daudé
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=fcf6d003-36b2-9e8c-4708-58293a610a6e@redhat.com \
--to=lersek@redhat.com \
--cc=philmd@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).