From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Vasily Philipov" <vasilyf@mellanox.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3 1/2] net/mlx4: split the definitions to the header file
Date: Mon, 20 Mar 2017 14:18:24 +0000 [thread overview]
Message-ID: <eb5485c0-7d0c-929c-5287-22e71866f129@intel.com> (raw)
In-Reply-To: <20170320091934.GF12013@autoinstall.dev.6wind.com>
On 3/20/2017 9:19 AM, Nélio Laranjeiro wrote:
> On Sun, Mar 05, 2017 at 09:51:31AM +0200, Vasily Philipov wrote:
>> Make priv_lock/priv_unlock functions and some other structs/defines visible
>> from different source files by placing them into mlx4.h header.
>>
>> Signed-off-by: Vasily Philipov <vasilyf@mellanox.com>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Series applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2017-03-20 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 14:07 [dpdk-dev] [PATCH " Vasily Philipov
2017-02-21 14:07 ` [dpdk-dev] [PATCH 2/2] net/mlx4: support basic flow items and actions Vasily Philipov
2017-02-22 8:37 ` Nélio Laranjeiro
2017-02-22 10:10 ` Nélio Laranjeiro
2017-02-22 8:37 ` [dpdk-dev] [PATCH 1/2] net/mlx4: split the definitions to the header file Nélio Laranjeiro
2017-02-22 13:42 ` [dpdk-dev] [PATCH v2 " Vasily Philipov
2017-02-22 19:04 ` Ferruh Yigit
2017-02-23 10:44 ` Vasily Philipov
2017-03-06 9:24 ` Ferruh Yigit
2017-02-22 13:42 ` [dpdk-dev] [PATCH v2 2/2] net/mlx4: support basic flow items and actions Vasily Philipov
2017-03-05 7:51 ` [dpdk-dev] [PATCH v3 1/2] net/mlx4: split the definitions to the header file Vasily Philipov
2017-03-20 9:19 ` Nélio Laranjeiro
2017-03-20 14:18 ` Ferruh Yigit [this message]
2017-03-05 7:51 ` [dpdk-dev] [PATCH v3 2/2] net/mlx4: support basic flow items and actions Vasily Philipov
2017-03-20 9:19 ` Nélio Laranjeiro
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=eb5485c0-7d0c-929c-5287-22e71866f129@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=vasilyf@mellanox.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).