From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, david.marchand@redhat.com, anand.rawat@intel.com
Subject: Re: [dpdk-dev] [PATCH] eal: remove exec-env directory
Date: Tue, 2 Apr 2019 10:39:33 +0100 [thread overview]
Message-ID: <20190402093933.GD1470@bricha3-MOBL.ger.corp.intel.com> (raw)
Message-ID: <20190402093933.75lXIYiR8KGcUoZ743SKioUFgtH7Cu9P0q7dI-Hzrhg@z> (raw)
In-Reply-To: <20190401230712.31864-1-thomas@monjalon.net>
On Tue, Apr 02, 2019 at 01:07:12AM +0200, Thomas Monjalon wrote:
> Only one header file (rte_kni_common.h) was in the sub-directory
> include/exec-env/
> This file was installed in a sub-directory of the same name.
> Source and install directories are moved as below:
>
> lib/librte_eal/linux/eal/include/exec-env/
> -> lib/librte_eal/linux/eal/include/
>
> build/include/exec-env/
> -> build/include/
>
> The consequence is to have a file hierarchy a bit more flat.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> devtools/check-includes.sh | 1 -
> kernel/linux/kni/kni_dev.h | 2 +-
> kernel/linux/kni/kni_fifo.h | 2 +-
> kernel/linux/kni/kni_misc.c | 2 +-
> kernel/linux/kni/kni_net.c | 2 +-
> lib/librte_eal/freebsd/eal/Makefile | 3 +--
> lib/librte_eal/linux/eal/Makefile | 3 +--
> .../linux/eal/include/{exec-env => }/rte_kni_common.h | 0
> lib/librte_kni/rte_kni.c | 2 +-
> lib/librte_kni/rte_kni.h | 2 +-
> 10 files changed, 8 insertions(+), 11 deletions(-)
> rename lib/librte_eal/linux/eal/include/{exec-env => }/rte_kni_common.h (100%)
>
+1 for flattening our EAL hierarchy.
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2019-04-02 9:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 23:07 Thomas Monjalon
2019-04-01 23:07 ` Thomas Monjalon
2019-04-02 9:39 ` Bruce Richardson [this message]
2019-04-02 9:39 ` Bruce Richardson
2019-04-02 14:43 ` Ferruh Yigit
2019-04-02 14:43 ` Ferruh Yigit
2019-04-02 9:57 ` David Marchand
2019-04-02 9:57 ` David Marchand
2019-04-02 10:03 ` Thomas Monjalon
2019-04-02 10:03 ` Thomas Monjalon
2019-04-02 15:13 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2019-04-02 15:13 ` Thomas Monjalon
2019-04-02 19:30 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2019-04-02 19:30 ` Thomas Monjalon
2019-04-02 19:46 ` David Marchand
2019-04-02 19:46 ` David Marchand
2019-04-02 19:50 ` Thomas Monjalon
2019-04-02 19:50 ` Thomas Monjalon
2019-04-03 8:41 ` David Marchand
2019-04-03 8:41 ` David Marchand
2019-04-02 19:52 ` Ferruh Yigit
2019-04-02 19:52 ` Ferruh Yigit
2019-04-02 19:55 ` David Marchand
2019-04-02 19:55 ` David Marchand
2019-04-02 19:57 ` Ferruh Yigit
2019-04-02 19:57 ` Ferruh Yigit
2019-04-02 20:04 ` David Marchand
2019-04-02 20:04 ` David Marchand
2019-04-02 20:09 ` Thomas Monjalon
2019-04-02 20:09 ` Thomas Monjalon
2019-04-03 13:34 ` Bruce Richardson
2019-04-03 13:34 ` Bruce Richardson
2019-04-02 19:50 ` Ferruh Yigit
2019-04-02 19:50 ` 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=20190402093933.GD1470@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anand.rawat@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--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).