From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Hunt, David" <david.hunt@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Hunt, David" <david.hunt@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1 3/3] lib/power: clarify comment on priority core
Date: Thu, 2 May 2019 16:14:07 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23F60C094@IRSMSX103.ger.corp.intel.com> (raw)
Message-ID: <20190502161407.PuM1GNW0WOfduG5p55965ObnjQg1pWnFrHJIyFo-yJY@z> (raw)
In-Reply-To: <20190502111815.29343-3-david.hunt@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of David Hunt
> Sent: Thursday, May 2, 2019 12:18 PM
> To: dev@dpdk.org
> Cc: Hunt, David <david.hunt@intel.com>
> Subject: [dpdk-dev] [PATCH v1 3/3] lib/power: clarify comment on priority
> core
>
> As part of the documentation update on the changes made to the power
> library for 19.05, information on SST-BF was added. This patch updates the
> comment to clarify that a priority core is an SST-BF high frequency core.
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2019-05-02 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 11:18 [dpdk-dev] [PATCH v1 1/3] doc/distributor: add SST-BF enhancement info David Hunt
2019-05-02 11:18 ` David Hunt
2019-05-02 11:18 ` [dpdk-dev] [PATCH v1 2/3] doc: add release note for power changes David Hunt
2019-05-02 11:18 ` David Hunt
2019-05-02 15:55 ` Mcnamara, John
2019-05-02 15:55 ` Mcnamara, John
2019-05-03 20:17 ` Thomas Monjalon
2019-05-03 20:17 ` Thomas Monjalon
2019-05-02 11:18 ` [dpdk-dev] [PATCH v1 3/3] lib/power: clarify comment on priority core David Hunt
2019-05-02 11:18 ` David Hunt
2019-05-02 16:14 ` Mcnamara, John [this message]
2019-05-02 16:14 ` Mcnamara, John
2019-05-02 15:53 ` [dpdk-dev] [PATCH v1 1/3] doc/distributor: add SST-BF enhancement info Mcnamara, John
2019-05-02 15:53 ` Mcnamara, John
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=B27915DBBA3421428155699D51E4CFE23F60C094@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
/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).