From: "Abner Chang" <abner.chang@hpe.com>
To: Gerd Hoffmann <kraxel@redhat.com>, Ard Biesheuvel <ardb@kernel.org>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
gaoliming <gaoliming@byosoft.com.cn>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Leif Lindholm <leif@nuviainc.com>, "Ni, Ray" <ray.ni@intel.com>,
"Schaefer, Daniel" <daniel.schaefer@hpe.com>,
Sunil V L <sunilvl@ventanamicro.com>,
"Ard Biesheuvel" <ardb+tianocore@kernel.org>
Subject: Re: [edk2-devel] [RFC] RISC-V QEMU virtual package
Date: Mon, 6 Sep 2021 13:04:56 +0000 [thread overview]
Message-ID: <CS1PR8401MB114429C4F351EB1A50E22E2AFFD29@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20210906121913.v5xkgighq4r67fe3@sirius.home.kraxel.org>
Ok thanks, do we need the two steps to migrate FDT modules under OvmfPkg/?
1. One patch set to clone those modules under OvmfPkg/
2. One patch set of ArmVirtPkg change to use those modules and deletes the ones under ArmVirtPkg/.
Or we just do all at once? I prefer to have two steps. How do you think?
Another question, who would like to be the reviewers of OvmfPkg/Fdt/*? Any volunteers from CC list?
Thanks
Abner
> -----Original Message-----
> From: Gerd Hoffmann [mailto:kraxel@redhat.com]
> Sent: Monday, September 6, 2021 8:19 PM
> To: Ard Biesheuvel <ardb@kernel.org>
> Cc: Yao, Jiewen <jiewen.yao@intel.com>; Chang, Abner (HPS SW/FW
> Technologist) <abner.chang@hpe.com>; devel@edk2.groups.io; gaoliming
> <gaoliming@byosoft.com.cn>; Ard Biesheuvel <ard.biesheuvel@arm.com>;
> Kinney, Michael D <michael.d.kinney@intel.com>; Leif Lindholm
> <leif@nuviainc.com>; Ni, Ray <ray.ni@intel.com>; Schaefer, Daniel
> <daniel.schaefer@hpe.com>; Sunil V L <sunilvl@ventanamicro.com>; Ard
> Biesheuvel <ardb+tianocore@kernel.org>
> Subject: Re: [edk2-devel] [RFC] RISC-V QEMU virtual package
>
> Hi,
>
> On Mon, Sep 06, 2021 at 02:04:48PM +0200, Ard Biesheuvel wrote:
> > On Mon, 6 Sept 2021 at 13:44, Yao, Jiewen <jiewen.yao@intel.com> wrote:
> > >
> > > I think it makes sense to put Fdt to OvmfPkg. I suggest an Fdt folder and
> put all things there.
> > >
> > > I also think we define Fdt feature in
> https://github.com/tianocore/edk2/blob/master/Maintainers.txt to add
> reviewer there to help review the code.
> > >
> >
> > Agreed.
>
> Agreeing too.
>
> take care,
> Gerd
next prev parent reply other threads:[~2021-09-06 13:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 3:15 [RFC] RISC-V QEMU virtual package Abner Chang
2021-09-06 1:06 ` 回复: [edk2-devel] " gaoliming
2021-09-06 4:16 ` Abner Chang
2021-09-06 6:16 ` Yao, Jiewen
2021-09-06 11:08 ` Abner Chang
2021-09-06 11:44 ` Yao, Jiewen
2021-09-06 12:04 ` Ard Biesheuvel
2021-09-06 12:19 ` Gerd Hoffmann
2021-09-06 13:04 ` Abner Chang [this message]
2021-09-07 1:09 ` 回复: " gaoliming
2021-09-07 2:31 ` Abner Chang
2021-09-07 7:18 ` Gerd Hoffmann
2021-09-07 17:22 ` Leif Lindholm
2021-09-08 12:31 ` Abner Chang
2021-09-08 13:37 ` Gerd Hoffmann
2021-09-08 15:33 ` Abner Chang
2021-09-08 15:53 ` Leif Lindholm
2021-09-09 5:23 ` Gerd Hoffmann
2021-09-10 0:08 ` Abner Chang
2021-09-10 9:54 ` Leif Lindholm
2021-09-10 10:06 ` Ni, Ray
2021-09-11 0:52 ` Abner Chang
[not found] ` <16A39EA413775DFC.29279@groups.io>
2021-09-18 6:46 ` Abner Chang
[not found] ` <16A5D7B7D6218B9A.31588@groups.io>
2021-09-18 7:00 ` Abner Chang
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=CS1PR8401MB114429C4F351EB1A50E22E2AFFD29@CS1PR8401MB1144.NAMPRD84.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