From: Thomas Monjalon <thomas@monjalon.net>
To: "Shaikh, Shahed" <Shahed.Shaikh@cavium.com>
Cc: dev@dpdk.org, "Mody, Rasesh" <Rasesh.Mody@cavium.com>,
Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: Re: [PATCH 5/7] doc: list NPAR as supported feature in qede
Date: Sun, 06 Aug 2017 12:43:29 +0200 [thread overview]
Message-ID: <1601191.nyU60gEuCs@xps> (raw)
In-Reply-To: <BLUPR0701MB739C9F7F85376453E9C69C29FB70@BLUPR0701MB739.namprd07.prod.outlook.com>
> > From: Shahed Shaikh <Shahed.Shaikh@cavium.com>
> >
> > Existing qede PMD code already supports NPAR feature.
> > So adding this in "Supported Features" section after testing it with latest
> > DPDK.
> >
> > Also, add myself to the list of maintainers of qede PMD
>
> Acked-by: Rasesh Mody <rasesh.mody@cavium.com>
Applied, thanks
next prev parent reply other threads:[~2017-08-06 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 10:19 [PATCH 1/7] net/qede/base: fix recovery from previous ungraceful exit Rasesh Mody
2017-07-24 10:19 ` [PATCH 2/7] net/qede: fix incorrect queue id for 100G Rasesh Mody
2017-07-24 10:19 ` [PATCH 3/7] net/qede/base: fix for adapter specific stats Rasesh Mody
2017-07-24 10:19 ` [PATCH 4/7] net/qede: fix inner L3/L4 chksum offload for tunnel frames Rasesh Mody
2017-07-24 10:19 ` [PATCH 5/7] doc: list NPAR as supported feature in qede Rasesh Mody
2017-07-28 15:56 ` Mcnamara, John
2017-08-05 5:56 ` Mody, Rasesh
2017-08-06 10:43 ` Thomas Monjalon [this message]
2017-07-24 10:19 ` [PATCH 6/7] net/qede: fix chip details print Rasesh Mody
2017-07-24 10:19 ` [PATCH 7/7] net/qede: update PMD version 2.5.2.1 Rasesh Mody
2017-07-31 17:53 ` [PATCH 1/7] net/qede/base: fix recovery from previous ungraceful exit Ferruh Yigit
2017-08-05 5:59 ` Mody, Rasesh
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=1601191.nyU60gEuCs@xps \
--to=thomas@monjalon.net \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=Rasesh.Mody@cavium.com \
--cc=Shahed.Shaikh@cavium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.