From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rami Rosen <roszenrami@gmail.com>, Jeff Shaw <jeffrey.b.shaw@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: remove unnecessary dirent.h include
Date: Mon, 17 Dec 2018 23:58:11 +0000 [thread overview]
Message-ID: <a5ff1b0f-41fa-9162-a566-fd84a5e15182@intel.com> (raw)
In-Reply-To: <CAKoUArnTHFe6eFM=RaFsZjZbCNxaVA4BFf+ZDKV+dQ-eh6wBgw@mail.gmail.com>
On 12/17/2018 3:42 PM, Rami Rosen wrote:
> On Fri, 14 Dec 2018 at 18:43, Jeff Shaw <jeffrey.b.shaw@intel.com> wrote:
>>
>> Prior to this patch, the two affected .c files include <dirent.h>
>> unnecessarily. This commit removes the include lines.
>>
>> Signed-off-by: Jeff Shaw <jeffrey.b.shaw@intel.com>
>
> Reviewed-by: Rami Rosen <ramirose@gmail.com>
>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-12-17 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 16:40 Jeff Shaw
2018-12-17 15:42 ` Rami Rosen
2018-12-17 23:58 ` Ferruh Yigit [this message]
2018-12-19 0:30 ` Thomas Monjalon
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=a5ff1b0f-41fa-9162-a566-fd84a5e15182@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jeffrey.b.shaw@intel.com \
--cc=roszenrami@gmail.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).