DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Kearney, Tadhg" <tadhg.kearney@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "dave.hunt@intel.com" <dave.hunt@intel.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: RE: [PATCH v1 0/4] add uncore api to be called through l3fwd-power
Date: Mon, 11 Jul 2022 16:56:31 +0000	[thread overview]
Message-ID: <BYAPR11MB3366B33C6996289F8C4CC295FF879@BYAPR11MB3366.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220711162300.3308684-1-tadhg.kearney@intel.com>



> -----Original Message-----
> From: Kearney, Tadhg <tadhg.kearney@intel.com>
> Sent: Monday, July 11, 2022 5:23 PM
> To: dev@dpdk.org
> Cc: dave.hunt@intel.com; Burakov, Anatoly <anatoly.burakov@intel.com>;
> Pattan, Reshma <reshma.pattan@intel.com>; Kearney, Tadhg
> <tadhg.kearney@intel.com>
> Subject: [PATCH v1 0/4] add uncore api to be called through l3fwd-power
> 

The below patch  should be the 1st patch in the series. As the macros in this patch are used by rest of the patches in the series.

[PATCH v1 4/4] config: add uncore defines for x86 

Thanks,
Reshma

      parent reply	other threads:[~2022-07-11 16:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 16:22 tadhgkearney
2022-07-11 16:22 ` [PATCH v1 1/4] power: add uncore api to power library tadhgkearney
2022-07-11 16:36   ` Stephen Hemminger
2022-07-14 14:56     ` Kearney, Tadhg
2022-07-14 16:03       ` Stephen Hemminger
2022-07-11 16:22 ` [PATCH v1 2/4] l3fwd-power: add option to call uncore api tadhgkearney
2022-07-11 16:22 ` [PATCH v1 3/4] test/power: add unit tests for " tadhgkearney
2022-07-11 16:23 ` [PATCH v1 4/4] config: add uncore defines for x86 tadhgkearney
2022-07-11 16:56 ` Pattan, Reshma [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=BYAPR11MB3366B33C6996289F8C4CC295FF879@BYAPR11MB3366.namprd11.prod.outlook.com \
    --to=reshma.pattan@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dave.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=tadhg.kearney@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).