From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"kraxel@redhat.com" <kraxel@redhat.com>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH v4 0/7] add support for virtio-mmio 1.0
Date: Fri, 27 Aug 2021 13:45:59 +0000 [thread overview]
Message-ID: <PH0PR11MB48859945A63F0DFA9303193E8CC89@PH0PR11MB4885.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210827134232.qvshcb42c7ctbxx5@sirius.home.kraxel.org>
Yes, please.
Feel free to submit your own PR.
As long as you did not label - PUSH, this CI just shows the test result. It will NOT merge automatically.
Thank you
Yao Jiewen
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Gerd
> Hoffmann
> Sent: Friday, August 27, 2021 9:43 PM
> To: Yao, Jiewen <jiewen.yao@intel.com>
> Cc: devel@edk2.groups.io
> Subject: Re: [edk2-devel] [PATCH v4 0/7] add support for virtio-mmio 1.0
>
> On Fri, Aug 27, 2021 at 11:35:42AM +0000, Yao, Jiewen wrote:
> > I am sorry, I mess up https://github.com/tianocore/edk2/pull/1917, please
> ignore that.
> >
> > This pull request is re-created at https://github.com/tianocore/edk2/pull/1918.
> >
> > Please take a look at 1918.
>
> Is there some way to run the CI before posting the patches?
>
> I could probably create a dummy pull request for that and delete it when
> the CI is done. That'll probably make gitlab send out a bunch of
> annoying notifications though ...
>
> thanks,
> Gerd
>
>
>
>
>
next prev parent reply other threads:[~2021-08-27 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 7:25 [PATCH v4 0/7] add support for virtio-mmio 1.0 Gerd Hoffmann
2021-08-19 7:25 ` [PATCH v4 1/7] OvmfPkg/Virtio10: Add virtio-mmio 1.0 defines Gerd Hoffmann
2021-08-19 7:25 ` [PATCH v4 2/7] OvmfPkg/VirtioMmioDeviceLib: Add virtio 1.0 detection Gerd Hoffmann
2021-08-19 7:25 ` [PATCH v4 3/7] OvmfPkg/VirtioMmioDeviceLib: virtio 1.0: Fix SetPageSize Gerd Hoffmann
2021-08-19 7:25 ` [PATCH v4 4/7] OvmfPkg/VirtioMmioDeviceLib: virtio 1.0: Fix SetQueueAddress Gerd Hoffmann
2021-08-19 7:25 ` [PATCH v4 5/7] OvmfPkg/VirtioMmioDeviceLib: virtio 1.0: Add default QueueNum Gerd Hoffmann
2021-08-19 7:25 ` [PATCH v4 6/7] OvmfPkg/VirtioMmioDeviceLib: virtio 1.0: Adapt feature bit handling Gerd Hoffmann
2021-08-19 7:25 ` [PATCH v4 7/7] OvmfPkg/VirtioMmioDeviceLib: enable virtio 1.0 Gerd Hoffmann
2021-08-19 9:26 ` [edk2-devel] [PATCH v4 0/7] add support for virtio-mmio 1.0 Philippe Mathieu-Daudé
2021-08-20 7:20 ` Yao, Jiewen
2021-08-27 10:35 ` Yao, Jiewen
[not found] ` <169F236B4CC08BB7.32747@groups.io>
2021-08-27 11:35 ` Yao, Jiewen
2021-08-27 13:42 ` Gerd Hoffmann
2021-08-27 13:45 ` Yao, Jiewen [this message]
2021-08-27 13:46 ` Ard Biesheuvel
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=PH0PR11MB48859945A63F0DFA9303193E8CC89@PH0PR11MB4885.namprd11.prod.outlook.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