From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: remove unused struct forward declaration
Date: Fri, 16 Mar 2018 19:39:12 +0530 [thread overview]
Message-ID: <CAJ5mUsXVZjcBXTLBz+KVcD4gA=cSKusuk5R43skk6xZnxuTqHw@mail.gmail.com> (raw)
In-Reply-To: <20180316111450.299132-1-ferruh.yigit@intel.com>
On Fri, Mar 16, 2018 at 4:44 PM, Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> lib/librte_ether/rte_ethdev.h | 2 --
> 1 file changed, 2 deletions(-)
>
With movement to rte_ethdev_core.h, this looks correct.
Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
next prev parent reply other threads:[~2018-03-16 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 11:14 Ferruh Yigit
2018-03-16 14:09 ` Shreyansh Jain [this message]
2018-03-16 14:29 ` Ferruh Yigit
2018-03-27 18:35 ` Ferruh Yigit
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='CAJ5mUsXVZjcBXTLBz+KVcD4gA=cSKusuk5R43skk6xZnxuTqHw@mail.gmail.com' \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas@monjalon.net \
/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).