From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rasesh Mody <rasesh.mody@cavium.com>,
dev@dpdk.org,
"john.mcnamara@intel.com thomas.monjalon"@6wind.com
Cc: Dept-EngDPDKDev@cavium.com
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: update QEDE pmd nic guide
Date: Fri, 10 Nov 2017 00:24:33 -0800 [thread overview]
Message-ID: <23fa7c03-1944-8cb5-77a4-c66bc644535b@intel.com> (raw)
In-Reply-To: <1510210340-5433-1-git-send-email-rasesh.mody@cavium.com>
On 11/8/2017 10:52 PM, Rasesh Mody wrote:
> Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
Series applied to dpdk/master, thanks.
prev parent reply other threads:[~2017-11-10 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 6:52 Rasesh Mody
2017-11-09 6:52 ` [dpdk-dev] [PATCH 2/2] net/qede: fix default config option Rasesh Mody
2017-11-09 22:48 ` Ferruh Yigit
2017-11-09 22:57 ` Patil, Harish
2017-11-09 23:00 ` Patil, Harish
2017-11-09 23:07 ` Ferruh Yigit
2017-11-09 23:16 ` Patil, Harish
2017-11-10 1:07 ` Ferruh Yigit
2017-11-10 1:53 ` Mody, Rasesh
2017-11-10 2:03 ` Ferruh Yigit
2017-11-10 8:24 ` Ferruh Yigit [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=23fa7c03-1944-8cb5-77a4-c66bc644535b@intel.com \
--to=ferruh.yigit@intel.com \
--cc="john.mcnamara@intel.com thomas.monjalon"@6wind.com \
--cc=Dept-EngDPDKDev@cavium.com \
--cc=dev@dpdk.org \
--cc=rasesh.mody@cavium.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).