public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Duran, Leo" <leo.duran@amd.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
	"Zhu, Yonghong" <yonghong.zhu@intel.com>,
	 "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] BaseTools/Source/C/GenFv/GenFvInternalLib.c
Date: Sun, 14 Aug 2016 21:24:39 +0200	[thread overview]
Message-ID: <CAKv+Gu9VzwmgHZiHarZxiTveS5ro6R0jm4XVejzj=E-FJgVSLQ@mail.gmail.com> (raw)
In-Reply-To: <DM5PR12MB1243666A1D87D74496A97402F9110@DM5PR12MB1243.namprd12.prod.outlook.com>

On 14 August 2016 at 17:05, Duran, Leo <leo.duran@amd.com> wrote:
>
>> -----Original Message-----
>> From: Gao, Liming [mailto:liming.gao@intel.com]
>> Sent: Friday, August 12, 2016 3:32 AM
>> To: Duran, Leo <leo.duran@amd.com>; edk2-devel@lists.01.org
>> Cc: Zhu, Yonghong <yonghong.zhu@intel.com>
>> Subject: RE: [PATCH] BaseTools/Source/C/GenFv/GenFvInternalLib.c
>>
>> Duran:
>>   Reusing FvForceRebase flag is a good idea to resolve this issue. I agree your
>> change. Reviewed-by: Liming Gao <liming.gao@intel.com>
>>
> [Duran, Leo]
> Excellent, thanks!
>
> Please advise on "next steps":
> 1) Do we need a reply from Yonghong Zhu?
> 2) When would it be reasonable to expect integration of this code into mainline?
>

Hi all,

I pushed this (with Liming's R-b) as

adb6ac256338 BaseTools/GenFv: Account for rebase of FV section
containing VTF file

Thanks,
Ard.


  reply	other threads:[~2016-08-14 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 15:23 [PATCH] BaseTools/Source/C/GenFv/GenFvInternalLib.c Leo Duran
2016-08-11 15:23 ` Leo Duran
2016-08-12  8:32   ` Gao, Liming
2016-08-14 15:05     ` Duran, Leo
2016-08-14 19:24       ` Ard Biesheuvel [this message]
2016-08-15  0:15         ` Zhu, Yonghong
2016-08-15 13:13           ` Duran, Leo
2016-08-15 15:16             ` Gao, Liming

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='CAKv+Gu9VzwmgHZiHarZxiTveS5ro6R0jm4XVejzj=E-FJgVSLQ@mail.gmail.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