From: Thomas Monjalon <thomas@monjalon.net>
To: Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com, vipin.varghese@intel.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v1] mk: fix external build failure
Date: Mon, 05 Feb 2018 19:26:57 +0100 [thread overview]
Message-ID: <6472052.tuBDJin1pE@xps> (raw)
In-Reply-To: <20180205102243.16445-1-marko.kovacevic@intel.com>
05/02/2018 11:22, Marko Kovacevic:
> Updated the make build to fix external build issues
>
> Fixes: 3a5c339d51a4 ("mk: support renamed Makefile in external project")
> Cc: stable@dpdk.org
>
> Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-02-05 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 10:22 [dpdk-dev] " Marko Kovacevic
2018-02-05 10:37 ` Thomas Monjalon
2018-02-05 10:53 ` Kovacevic, Marko
2018-02-05 14:07 ` Thomas Monjalon
2018-02-05 22:38 ` Thomas Monjalon
2018-02-05 15:45 ` [dpdk-dev] [PATCH v2] " Marko Kovacevic
2018-02-05 22:39 ` Thomas Monjalon
2018-02-05 18:26 ` Thomas Monjalon [this message]
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=6472052.tuBDJin1pE@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=olivier.matz@6wind.com \
--cc=vipin.varghese@intel.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).