From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, rebecca@bsdio.com
Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>,
Andrew Fish <afish@apple.com>, Leif Lindholm <leif@nuviainc.com>,
Jordan L Justen <jordan.l.justen@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] Add BhyvePkg, to support the bhyve hypervisor
Date: Fri, 31 Jul 2020 15:10:42 +0200 [thread overview]
Message-ID: <48628363-3c1b-7d24-6dbc-95e739ac389d@redhat.com> (raw)
In-Reply-To: <52be7a58-9e2b-92a0-5f15-22a9dd59b0e4@redhat.com>
On 07/31/20 15:07, Laszlo Ersek wrote:
> On 07/31/20 07:17, Rebecca Cran wrote:
>> On 7/13/20 2:25 PM, Rebecca Cran wrote:
>>
>>> On 7/13/20 12:09 PM, Laszlo Ersek wrote:
>>>
>>>> Can you please ping me when the PatchCheck.py problem has been solved,
>>>> so I can go ahead with the merge?
>>>
>>> Will do.
>>
>>
>> Hi Laszlo,
>>
>>
>> I just rebased the bhyve commit against the latest edk2 master with no
>> conflicts, and all CI checks passed
>> (https://github.com/tianocore/edk2/pull/841).
>>
>> So I think it's ready to go into the tree.
>
> Thanks for the ping.
>
> I've had your patch applied locally, from the list, on top of
> then-master HEAD f45e3a4afa65, ready for pushing.
>
> I've now fetched your branch (from your PR above), at commit
> d6ec30afebe6. I've also rebased my local branch (see above) on top of
> current master (137c2c6eff67). Your rebase and my rebase are identical
> (except my version carries your original Message-Id for the patch, plus
> my Acked-by given earlier).
>
> Thus I've submitted the following PR, using my rebased branch (including
> the Message-Id and Acked-by tags):
>
> https://github.com/tianocore/edk2/pull/842
>
> Merged as commit 656419f922c0.
... We should have updated the subject line from
Add BhyvePkg, to support the bhyve hypervisor
to
OvmfPkg: add OvmfPkg/Bhyve, to support the bhyve hypervisor
I hope the rest of the community will forgive us for missing that.
My apologies.
Laszlo
> Thank you for the contribution!
>
> Please follow up with a patch for "Maintainers.txt", as discussed up-thread.
>
> Thanks!
> Laszlo
>
next prev parent reply other threads:[~2020-07-31 13:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 5:41 [PATCH 0/1] Add BhyvePkg, to support the bhyve hypervisor Rebecca Cran
2020-07-13 5:41 ` [PATCH 1/1] " Rebecca Cran
2020-07-13 16:16 ` [edk2-devel] " Laszlo Ersek
2020-07-13 20:24 ` Rebecca Cran
2020-07-13 16:55 ` Laszlo Ersek
2020-07-13 18:09 ` Laszlo Ersek
2020-07-13 20:25 ` Rebecca Cran
[not found] ` <162169B0F92549B8.20689@groups.io>
2020-07-31 5:17 ` Rebecca Cran
2020-07-31 13:07 ` Laszlo Ersek
2020-07-31 13:10 ` Laszlo Ersek [this message]
2020-07-31 17:32 ` Sean
2020-07-31 20:28 ` Rebecca Cran
2020-07-31 21:14 ` Laszlo Ersek
2020-08-01 15:54 ` Laszlo Ersek
2020-08-01 21:10 ` Laszlo Ersek
2020-07-13 5:43 ` [PATCH 0/1] " Liming Gao
2020-07-13 5:48 ` Rebecca Cran
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=48628363-3c1b-7d24-6dbc-95e739ac389d@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