From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: "Ni, Ray" <ray.ni@intel.com>
Cc: "Wu, Hao A" <hao.a.wu@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Zeng, Star" <star.zeng@intel.com>,
"lersek@redhat.com" <lersek@redhat.com>,
"Gao, Liming" <liming.gao@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Andrew Fish <afish@apple.com>
Subject: Re: [edk2-devel] [Patch V2] EmulatorPkg: don't diaplay the cpu current speed
Date: Mon, 10 Jun 2019 09:37:00 +0200 [thread overview]
Message-ID: <CAKv+Gu_jUsCeKowae2X6fmpgP6RVG+deERaD9P8qzDnZWci7Vw@mail.gmail.com> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5C19CBB2@SHSMSX104.ccr.corp.intel.com>
On Mon, 10 Jun 2019 at 09:33, Ni, Ray <ray.ni@intel.com> wrote:
>
> > > Hao,
> > > Can you please list the detailed sub-directories/modules/libraries for
> > > each major feature, including those that are not covered by the major
> > features?
> > > This avoid misunderstanding and is also needed by the Maintainers.txt.
> >
> > Hello Ray,
> >
> > Okay. I can do that.
> >
> > But I would like to collect some feedbacks on significant missing feature in
> > the list or some suggestion on the granularity of the feature first before your
> > request.
>
> I am ok.
>
That sounds like a good idea.
But currrently, this discussion is taking place in the context of the
thread '[edk2-devel] [Patch V2] EmulatorPkg: don't diaplay the cpu
current speed' which may not be of interest to everybody. So could you
please start a new [RFC] thread with the proposed subdivision, and
keep the same people on cc? Thanks.
next prev parent reply other threads:[~2019-06-10 7:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 6:45 [Patch V2] EmulatorPkg: don't diaplay the cpu current speed Zhiguang Liu
2019-06-03 6:51 ` [edk2-devel] " Ni, Ray
[not found] ` <15A49DA9FFA456B0.4546@groups.io>
2019-06-04 8:50 ` Ni, Ray
2019-06-04 11:53 ` Ard Biesheuvel
2019-06-04 13:40 ` Liming Gao
2019-06-04 13:41 ` Ard Biesheuvel
2019-06-04 14:19 ` Liming Gao
2019-06-05 1:10 ` Ni, Ray
2019-06-05 8:03 ` Laszlo Ersek
2019-06-05 14:31 ` Zeng, Star
2019-06-10 6:01 ` Wu, Hao A
2019-06-10 6:13 ` Yao, Jiewen
2019-06-10 6:20 ` Wu, Hao A
2019-06-10 7:16 ` Ni, Ray
2019-06-10 7:32 ` Wu, Hao A
2019-06-10 7:33 ` Ni, Ray
2019-06-10 7:37 ` Ard Biesheuvel [this message]
2019-06-10 8:07 ` Wu, Hao A
2019-06-10 10:50 ` Ard Biesheuvel
2019-06-11 15:19 ` Laszlo Ersek
2019-06-10 7:39 ` Yao, Jiewen
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=CAKv+Gu_jUsCeKowae2X6fmpgP6RVG+deERaD9P8qzDnZWci7Vw@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