From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: fix combined library building
Date: Wed, 10 Jun 2015 12:23:45 +0200 [thread overview]
Message-ID: <2456894.VjTTAY7Bek@xps13> (raw)
In-Reply-To: <5577A569.2080807@cn.fujitsu.com>
2015-06-10 10:48, Li Wei:
> On 06/09/2015 05:37 PM, Sergio Gonzalez Monroy wrote:
> > The combined lib was being created after building the lib root dir.
> > With the new directory hierarchy, it should be created after the
> > drivers root dir instead.
> >
> > Fixes: 980ed498eb1dd0 ("drivers: create new directory")
> >
> > Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
>
> Tested-by: Li Wei <lw@cn.fujitsu.com>
Applied, thanks
prev parent reply other threads:[~2015-06-10 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 9:37 Sergio Gonzalez Monroy
2015-06-09 10:33 ` De Lara Guarch, Pablo
2015-06-10 2:48 ` Li Wei
2015-06-10 10:23 ` 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=2456894.VjTTAY7Bek@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=sergio.gonzalez.monroy@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).