DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"maryam.tahhan@intel.com" <maryam.tahhan@intel.com>,
	"reshma.pattan@intel.com" <reshma.pattan@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/procinfo: enhance port mempool and crypto info
Date: Wed, 15 Jul 2020 00:43:44 +0000	[thread overview]
Message-ID: <5027994b-359f-48c2-907c-ef57e57cc1bb@nxp.com> (raw)
In-Reply-To: <20200714170737.02f7dacb@hermes.lan>

Yes. Please create one series.

Get BlueMail for Android<http://www.bluemail.me/r?b=15860>
On 15 Jul 2020, at 5:37 AM, Stephen Hemminger <stephen@networkplumber.org<mailto:stephen@networkplumber.org>> wrote:

On Mon, 13 Jul 2020 03:49:30 +0000
Hemant Agrawal <hemant.agrawal@nxp.com> wrote:

 -----Original Message-----
 From: Stephen Hemminger <stephen@networkplumber.org>
 Sent: Sunday, July 12, 2020 8:42 AM
 To: Hemant Agrawal <hemant.agrawal@nxp.com>
 Cc: dev@dpdk.org; maryam.tahhan@intel.com; reshma.pattan@intel.com
 Subject: Re: [dpdk-dev] [PATCH v2] app/procinfo: enhance port mempool and crypto info
 Importance: High

 On Sat, 11 Jul 2020 15:23:43 +0530
 Hemant Agrawal <hemant.agrawal@nxp.com> wrote:

 This patch enhances the port info for more details about the port and
 queues.
 This patch also add support to get info about the mempool ops and
 security context for crypto devices.

 Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>

 What ever happened to my procinfo patch series.


 [Hemant] I will review and rebase my patch over your series.
 You could have informed me about it during v1 review.

 https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.dpdk.org%2Fpatch%2F69877%2F&amp;data=02%7C01%7Chemant.agrawal%40nxp.com%7C4fecf7458e2b48b0a34e08d828531b83%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637303684690631766&amp;sdata=oZltIDgCgHTDJm4Mgs9VCrHbpUZVIREmgscZW7r2XSw%3D&amp;reserved=0

How about I make one series with yours added, it will be easier to merge

  reply	other threads:[~2020-07-15  0:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 16:06 [dpdk-dev] [PATCH] app/procinfo: enhance port and mempool info Hemant Agrawal
2020-07-10 18:07 ` Stephen Hemminger
2020-07-11  9:53 ` [dpdk-dev] [PATCH v2] app/procinfo: enhance port mempool and crypto info Hemant Agrawal
2020-07-12  3:12   ` Stephen Hemminger
2020-07-13  3:49     ` Hemant Agrawal
2020-07-15  0:07       ` Stephen Hemminger
2020-07-15  0:43         ` Hemant Agrawal [this message]
2020-07-13  9:57   ` Pattan, Reshma
2020-07-13 13:15   ` [dpdk-dev] [PATCH v3 1/2] app/proc-info: enhance mempool to print ops name Hemant Agrawal
2020-07-13 13:15     ` [dpdk-dev] [PATCH v3 2/2] app/proc-info: add crypto security context info Hemant Agrawal

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=5027994b-359f-48c2-907c-ef57e57cc1bb@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=maryam.tahhan@intel.com \
    --cc=reshma.pattan@intel.com \
    --cc=stephen@networkplumber.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).