From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Rasesh Mody <rasesh.mody@qlogic.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
Dept-EngDPDKDev@qlogic.com,
Harish Patil <harish.patil@qlogic.com>,
remy.horton@intel.com
Subject: Re: [dpdk-dev] [PATCH v5 2/5] bnx2x: add xstats support
Date: Tue, 28 Jun 2016 16:34:14 +0200 [thread overview]
Message-ID: <1669794.y54etZhKHN@xps13> (raw)
In-Reply-To: <1463011585-15429-2-git-send-email-rasesh.mody@qlogic.com>
2016-05-11 17:06, Rasesh Mody:
> Add extended stats support to provide additional statistical info.
>
> Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com>
> Signed-off-by: Harish Patil <harish.patil@qlogic.com>
This bnx2x patch and a qede one cannot be merged in master tree
because of an API change:
http://dpdk.org/commit/bd6aa172
http://dpdk.org/commit/e2aae1c1
Please could you rework this patch for RC2?
Sorry for the inconvenience, I should have caught it earlier.
We'll try to synchronize the branches more often in future.
next prev parent reply other threads:[~2016-06-28 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 0:06 [dpdk-dev] [PATCH v5 1/5] bnx2x: fixed stats get Rasesh Mody
2016-05-12 0:06 ` [dpdk-dev] [PATCH v5 2/5] bnx2x: add xstats support Rasesh Mody
2016-06-28 14:34 ` Thomas Monjalon [this message]
2016-06-29 0:09 ` Rasesh Mody
2016-05-12 0:06 ` [dpdk-dev] [PATCH v5 3/5] bnx2x: restructure Tx routine Rasesh Mody
2016-05-12 0:06 ` [dpdk-dev] [PATCH v5 4/5] bnx2x: use single doorbell for TX Rasesh Mody
2016-05-12 0:06 ` [dpdk-dev] [PATCH v5 5/5] bnx2x: update driver version to 1.0.1.1 Rasesh Mody
2016-06-08 16:15 ` [dpdk-dev] [PATCH v5 1/5] bnx2x: fixed stats get Bruce Richardson
2016-06-10 10:08 ` Ferruh Yigit
2016-06-13 10:32 ` Ferruh Yigit
2016-06-13 10:47 ` [dpdk-dev] [PATCH] bnx2x: fix ICC compilation error Ferruh Yigit
2016-06-27 16:02 ` [dpdk-dev] [PATCH v2] bnx2x: fix icc " Ferruh Yigit
2016-06-27 23:21 ` Rasesh Mody
2016-06-29 9:53 ` Bruce Richardson
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=1669794.y54etZhKHN@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=Dept-EngDPDKDev@qlogic.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harish.patil@qlogic.com \
--cc=rasesh.mody@qlogic.com \
--cc=remy.horton@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).