From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>,
"Yao, Lei A" <lei.a.yao@intel.com>
Cc: "Mo, YufengX" <yufengx.mo@intel.com>
Subject: Re: [dts] [PATCH V2 0/8] power: power suite series support meson
Date: Thu, 17 Sep 2020 08:55:52 +0000 [thread overview]
Message-ID: <BN8PR11MB37151EB2D95A52F290E255399E3E0@BN8PR11MB3715.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200917010513.15783-1-yufengx.mo@intel.com>
Acked-by: lihongx ma<lihongx.ma@intel.com>
Regards,
Ma,lihong
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of yufengmx
> Sent: Thursday, September 17, 2020 9:05 AM
> To: dts@dpdk.org; Yao, Lei A <lei.a.yao@intel.com>
> Cc: Mo, YufengX <yufengx.mo@intel.com>
> Subject: [dts] [PATCH V2 0/8] power: power suite series support meson
>
>
> v2:
> - quote ma,lihong
> - 'We have configure the app path in the config file, so it does not need
> re-combine the path of it in the suite.
> - So it does not need to judge the build method in the suite.'
>
> v1:
> - power: power suite series support meson.
>
prev parent reply other threads:[~2020-09-17 8:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 1:05 yufengmx
2020-09-17 1:05 ` [dts] [PATCH V2 1/8] power_bidirection_channel: " yufengmx
2020-09-17 1:05 ` [dts] [PATCH V2 2/8] power_empty_poll: " yufengmx
2020-09-17 1:05 ` [dts] [PATCH V2 3/8] power_pbf: " yufengmx
2020-09-17 1:05 ` [dts] [PATCH V2 4/8] power_pstate: " yufengmx
2020-09-17 1:05 ` [dts] [PATCH V2 5/8] power_telemetry: " yufengmx
2020-09-17 1:05 ` [dts] [PATCH V2 6/8] vm_pw_mgmt_policy: " yufengmx
2020-09-17 1:05 ` [dts] [PATCH V2 7/8] malicious_driver_event_indication: " yufengmx
2020-09-17 1:05 ` [dts] [PATCH V2 8/8] conf: power suite series " yufengmx
2020-09-23 8:57 ` Tu, Lijuan
2020-09-17 1:13 ` [dts] [PATCH V2 0/8] power: " Mo, YufengX
2020-09-17 8:55 ` Ma, LihongX [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-all 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=BN8PR11MB37151EB2D95A52F290E255399E3E0@BN8PR11MB3715.namprd11.prod.outlook.com \
--to=lihongx.ma@intel.com \
--cc=dts@dpdk.org \
--cc=lei.a.yao@intel.com \
--cc=yufengx.mo@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).