From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>
Cc: dev@dpdk.org, Hyong Youb Kim <hyonkim@cisco.com>
Subject: Re: [dpdk-dev] [PATCH v4 1/2] net/enic: move common Rx functions to a new header file
Date: Thu, 4 Oct 2018 17:15:28 +0100 [thread overview]
Message-ID: <f9a752cb-e1c6-c8ae-817b-bedafe5aa918@intel.com> (raw)
In-Reply-To: <20181003200928.27086-1-johndale@cisco.com>
On 10/3/2018 9:09 PM, John Daley wrote:
> From: Hyong Youb Kim <hyonkim@cisco.com>
>
> Move a number of Rx functions to the header file so that the avx2
> based Rx handler can use them.
>
> Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com>
> Reviewed-by: John Daley <johndale@cisco.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-10-04 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 2:16 [dpdk-dev] [PATCH " John Daley
2018-09-28 2:16 ` [dpdk-dev] [PATCH 2/2] net/enic: add AVX2 based vectorized Rx handler John Daley
2018-09-28 19:20 ` [dpdk-dev] [PATCH v2 1/2] net/enic: move common Rx functions to a new header file John Daley
2018-09-28 19:20 ` [dpdk-dev] [PATCH v2 2/2] net/enic: add AVX2 based vectorized Rx handler John Daley
2018-09-28 19:25 ` [dpdk-dev] [PATCH v2 1/2] net/enic: move common Rx functions to a new header file John Daley
2018-09-28 19:25 ` [dpdk-dev] [PATCH v2 2/2] net/enic: add AVX2 based vectorized Rx handler John Daley
2018-10-02 16:08 ` Ferruh Yigit
2018-10-03 13:00 ` Hyong Youb Kim
2018-10-03 20:09 ` [dpdk-dev] [PATCH v4 1/2] net/enic: move common Rx functions to a new header file John Daley
2018-10-03 20:09 ` [dpdk-dev] [PATCH v4 2/2] net/enic: add AVX2 based vectorized Rx handler John Daley
2018-10-04 16:15 ` 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=f9a752cb-e1c6-c8ae-817b-bedafe5aa918@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.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).