From: "Ard Biesheuvel" <ardb@kernel.org>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
"Corvin Köhne" <c.koehne@beckhoff.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
Rebecca Cran <quic_rcran@quicinc.com>,
"jiewen.yao@intel.com" <jiewen.yao@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
FreeBSD Virtualization <freebsd-virtualization@freebsd.org>,
Rebecca Cran <rebecca@bsdio.com>,
Peter Grehan <grehan@freebsd.org>
Subject: Re: [edk2-devel] [PATCH v5] OvmfPkg/Bhyve: add support for QemuFwCfg
Date: Mon, 2 May 2022 18:51:34 +0200 [thread overview]
Message-ID: <CAMj1kXEqgv8iuGWUO9y_1=ZQqX-BxM9BFbn2aLgqS8vp4xu+DA@mail.gmail.com> (raw)
In-Reply-To: <50129038bf3247a0b4c4433f2e1168c0@beckhoff.com>
On Mon, 2 May 2022 at 16:47, Corvin Köhne <c.koehne@beckhoff.com> wrote:
>
> Hi
>
> > CI runs on all pull requests, so just open a draft pull request, then
> > check pull request status.
>
> I know now. Thanks. I did so before sending v5 to the mailing list and
> all checks have passed.
> https://github.com/tianocore/edk2/pull/2830
>
> Maybe something went wrong when sending the patch to the mailing
> list. Wouldn't it be easier to cherry-pick the commit from my fork?
> https://github.com/Beckhoff/edk2/commit/e3bc7e1ecca29e1efc39ce811ace9028642c3228
> Or just merging my pull request?
>
Merged as #2841
Thanks all,
prev parent reply other threads:[~2022-05-02 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 13:08 [PATCH v5] OvmfPkg/Bhyve: add support for QemuFwCfg Corvin Köhne
2022-04-26 14:07 ` Yao, Jiewen
2022-04-26 14:23 ` [edk2-devel] " Rebecca Cran
2022-04-27 10:06 ` Corvin Köhne
2022-05-02 12:40 ` Gerd Hoffmann
2022-05-02 14:47 ` Corvin Köhne
2022-05-02 16:51 ` Ard Biesheuvel [this message]
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='CAMj1kXEqgv8iuGWUO9y_1=ZQqX-BxM9BFbn2aLgqS8vp4xu+DA@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