From: Panu Matilainen <pmatilai@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] reserve 'make install' for future use
Date: Wed, 25 Nov 2015 10:48:51 +0200 [thread overview]
Message-ID: <565575F3.2000304@redhat.com> (raw)
In-Reply-To: <20151124165426.GA18656@bricha3-MOBL3>
On 11/24/2015 06:54 PM, Bruce Richardson wrote:
> On Fri, Nov 06, 2015 at 02:04:54PM +0100, Thomas Monjalon wrote:
>> 2015-11-06 12:57, Bruce Richardson:
>>> So, any thoughts or comments on this? There has been lots of discussion in this
>>> general area but nothing yet going into the release to try and improve the situation.
>>>
>>> Are we just going to kick the problem down the road to the 2.3 release?
>>
>> I plan to check these patches in the coming days for an integration in 2.2.
>>
> Anything further on this?
> Any thoughts from anyone else about this whole area of a saner build/install
> system for DPDK and the various patches floating around.
Well, it seems we wont have a sane "make install" in 2.2 yet, but this
is at least a step in the right direction so +1 from me.
- Panu -
next prev parent reply other threads:[~2015-11-25 8:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 10:24 Bruce Richardson
2015-11-06 10:24 ` [dpdk-dev] [PATCH] mk: rename 'make install' to 'make sdk' Bruce Richardson
2015-11-06 12:57 ` [dpdk-dev] [PATCH] reserve 'make install' for future use Bruce Richardson
2015-11-06 13:04 ` Thomas Monjalon
2015-11-24 16:54 ` Bruce Richardson
2015-11-25 8:48 ` Panu Matilainen [this message]
2015-11-27 17:33 ` Thomas Monjalon
2015-11-30 11:08 ` Richardson, Bruce
2015-11-30 11:27 ` Thomas Monjalon
2015-11-30 11:41 ` Richardson, Bruce
2015-11-30 11:49 ` Bruce Richardson
2015-11-30 14:26 ` Thomas Monjalon
2015-12-04 15:57 ` Thomas Monjalon
2015-12-04 16:21 ` Richardson, Bruce
2015-11-30 12:26 ` Panu Matilainen
2015-11-30 14:19 ` 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=565575F3.2000304@redhat.com \
--to=pmatilai@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).