From: "Ni, Ray" <ray.ni@intel.com>
To: Sunil V L <sunilvl@ventanamicro.com>, Chao Li <lichao@loongson.cn>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
Laszlo Ersek <lersek@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] RFC: Folder layout change in UefiCpuPkg
Date: Mon, 15 Jan 2024 08:11:05 +0000 [thread overview]
Message-ID: <MN6PR11MB8244AAE2B72D0B663BD875BE8C6C2@MN6PR11MB8244.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ZaTUt/j9iz9b0AWf@sunil-laptop>
Yes. Fine to me. Thanks!
Thanks,
Ray
> -----Original Message-----
> From: Sunil V L <sunilvl@ventanamicro.com>
> Sent: Monday, January 15, 2024 2:46 PM
> To: Chao Li <lichao@loongson.cn>
> Cc: devel@edk2.groups.io; Ni, Ray <ray.ni@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; Laszlo Ersek <lersek@redhat.com>; Gerd
> Hoffmann <kraxel@redhat.com>
> Subject: Re: [edk2-devel] RFC: Folder layout change in UefiCpuPkg
>
> On Mon, Jan 15, 2024 at 02:17:09PM +0800, Chao Li wrote:
> > Ray and Sunil,
> >
> > I plan send two example PRs to github to show how to deal the INFs, one to
> > adjust current INF, and another PR to move the libraris to the current
> > folders. I hope after these two PRs are sent we can decide what to do with
> > the INF. What do you think of this plan?
> >
> >
> Hi Chao, That's fine with me.
>
> Thanks,
> Sunil
> > Thanks,
> > Chao
> > On 2024/1/15 13:44, Ni, Ray wrote:
> > > That will be great!
> > >
> > > Thanks,
> > > Ray
> > > > -----Original Message-----
> > > > From: Sunil V L<sunilvl@ventanamicro.com>
> > > > Sent: Monday, January 15, 2024 12:44 PM
> > > > To: Ni, Ray<ray.ni@intel.com>
> > > > Cc:devel@edk2.groups.io;lichao@loongson.cn; Kinney, Michael D
> > > > <michael.d.kinney@intel.com>; Laszlo Ersek<lersek@redhat.com>; Gerd
> > > > Hoffmann<kraxel@redhat.com>
> > > > Subject: Re: RFC: Folder layout change in UefiCpuPkg
> > > >
> > > > On Mon, Jan 15, 2024 at 01:13:03AM +0000, Ni, Ray wrote:
> > > > > Sunil,
> > > > > I am glad that you don't have concern about the direction.
> > > > >
> > > > > "RiscV" is good to me.
> > > > >
> > > > >
> > > > Thanks!, Ray. So, shall I send patches to reorganize this?
> > > >
> > > > Thanks,
> > > > Sunil
> > >
> > >
> > >
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#113806): https://edk2.groups.io/g/devel/message/113806
Mute This Topic: https://groups.io/mt/103679850/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-01-16 5:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 9:12 [edk2-devel] RFC: Folder layout change in UefiCpuPkg Ni, Ray
2024-01-12 9:57 ` Chao Li
2024-01-12 10:19 ` Sunil V L
2024-01-15 1:13 ` Ni, Ray
2024-01-15 4:44 ` Sunil V L
2024-01-15 5:44 ` Ni, Ray
2024-01-15 6:17 ` Chao Li
2024-01-15 6:46 ` Sunil V L
2024-01-15 8:11 ` Ni, Ray [this message]
2024-01-16 0:59 ` Chao Li
[not found] ` <17AAAE0FD29564BB.7072@groups.io>
2024-01-18 8:27 ` Chao Li
2024-01-19 10:17 ` Ni, Ray
2024-01-19 13:47 ` Laszlo Ersek
2024-01-23 3:10 ` Chang, Abner via groups.io
2024-01-23 4:39 ` Chao Li
2024-01-23 5:02 ` Chang, Abner via groups.io
2024-01-15 8:48 ` Laszlo Ersek
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=MN6PR11MB8244AAE2B72D0B663BD875BE8C6C2@MN6PR11MB8244.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