DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, Anand Rawat <anand.rawat@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal: remove exec-env directory
Date: Tue, 2 Apr 2019 21:46:28 +0200	[thread overview]
Message-ID: <CAJFAV8yj5KFqLZS7666hrCy_33qGjpAQC7BOUma=88S2BTWyew@mail.gmail.com> (raw)
Message-ID: <20190402194628.8ea8DJDaWiHU2ZIPlPj9X2IH2MfBk_PB__eAFMd0Soc@z> (raw)
In-Reply-To: <20190402193048.27410-1-thomas@monjalon.net>

On Tue, Apr 2, 2019 at 9:30 PM Thomas Monjalon <thomas@monjalon.net> 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
> in the makefile-based build.
> 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>
>

Looks good to me.
Reviewed-by: David Marchand <david.marchand@redhat.com>
Tested-by: David Marchand <david.marchand@redhat.com>


Bruce, while testing with meson, I noticed this:
kernel/linux/kni/meson.build:16: WARNING: Passed invalid keyword argument
"console".
WARNING: This will become a hard error in the future.
WARNING: Unknown keyword arguments in target rte_kni: console


-- 
David Marchand

  parent reply	other threads:[~2019-04-02 19:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 23:07 [dpdk-dev] [PATCH] " Thomas Monjalon
2019-04-01 23:07 ` Thomas Monjalon
2019-04-02  9:39 ` Bruce Richardson
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 [this message]
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='CAJFAV8yj5KFqLZS7666hrCy_33qGjpAQC7BOUma=88S2BTWyew@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=anand.rawat@intel.com \
    --cc=bruce.richardson@intel.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).