From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Nikhil Rao <nikhil.rao@intel.com>
Cc: ferruh.yigit@intel.com, lei.a.yao@intel.com, dev@dpdk.org,
stable@dpdk.org
Subject: Re: [PATCH] eventdev: make ethernet port identifiers 16 bit
Date: Thu, 10 May 2018 08:46:34 +0530 [thread overview]
Message-ID: <20180510031633.GA5608@jerin> (raw)
In-Reply-To: <1525893452-155596-1-git-send-email-nikhil.rao@intel.com>
-----Original Message-----
> Date: Thu, 10 May 2018 00:47:32 +0530
> From: Nikhil Rao <nikhil.rao@intel.com>
> To: jerin.jacob@caviumnetworks.com
> CC: ferruh.yigit@intel.com, lei.a.yao@intel.com, dev@dpdk.org, Nikhil Rao
> <nikhil.rao@intel.com>, stable@dpdk.org
> Subject: [PATCH] eventdev: make ethernet port identifiers 16 bit
> X-Mailer: git-send-email 1.8.3.1
>
> Supersedes the following posts:
> http://dpdk.org/ml/archives/dev/2018-May/100917.html
> http://dpdk.org/ml/archives/dev/2018-May/100426.html
Superseding details can go in comment section not in git commit.
Please add detailed git commit description like ferruh's patch.
Ferruh,
I am planning to take this patch after the proposed change, any
objection to Superseding the following?
> http://dpdk.org/ml/archives/dev/2018-May/100917.html
> http://dpdk.org/ml/archives/dev/2018-May/100426.html
>
> Fixes: 9c38b704d280 ("eventdev: add eth Rx adapter implementation")
> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> Cc: stable@dpdk.org
prev parent reply other threads:[~2018-05-10 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 19:17 [PATCH] eventdev: make ethernet port identifiers 16 bit Nikhil Rao
2018-05-09 20:52 ` [PATCH v2] " Nikhil Rao
2018-05-10 4:31 ` Jerin Jacob
2018-05-10 13:48 ` [dpdk-stable] " Thomas Monjalon
2018-05-10 14:30 ` Jerin Jacob
2018-05-10 14:54 ` Thomas Monjalon
2018-05-10 15:16 ` Jerin Jacob
2018-05-10 15:45 ` Thomas Monjalon
2018-05-10 16:11 ` Thomas Monjalon
2018-05-10 5:35 ` Jerin Jacob
2018-05-10 5:49 ` Jerin Jacob
2018-05-10 3:16 ` Jerin Jacob [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=20180510031633.GA5608@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lei.a.yao@intel.com \
--cc=nikhil.rao@intel.com \
--cc=stable@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.