From: Thomas Monjalon <thomas@monjalon.net>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [pull-request] next-pipeline 17.11 pre-rc1
Date: Thu, 12 Oct 2017 19:10:50 +0200 [thread overview]
Message-ID: <3569007.OBp7ulgCO0@xps> (raw)
In-Reply-To: <1507732847-100455-1-git-send-email-cristian.dumitrescu@intel.com>
Hi,
11/10/2017 16:40, Cristian Dumitrescu:
> The following changes since commit d65b3b1668f2037745407c3909c43d85a18692a6:
>
> vhost: fix false-positive warning from clang 5 (2017-10-11 13:56:34 +0200)
>
> are available in the git repository at:
>
> http://dpdk.org/git/next/dpdk-next-pipeline
>
> for you to fetch changes up to 5ba29c202060c8edadbc36d8c9c19be24bd95cac:
>
> deprecation: removed the librte_table notice (2017-10-11 15:07:45 +0100)
>
> ----------------------------------------------------------------
> Cristian Dumitrescu (8):
> initial commit
> removing startup file
> Merge branch 'master' of dpdk.org:dpdk-next-pipeline
> table: add key mask for hash tables
> test: update due to api changes in librte_table
> test-pipeline: update due to api changes in librte_table
> ip_pipeline: update due to api changes in librte_table
> deprecation: removed the librte_table notice
It cannot be integrated in RC1 because we must be able to compile
between each commit (to avoid breaking git bisect).
The first commit is very big and does several things.
Maybe you can split it and update the applications accordingly.
I have seen also that the .map file has some issues (blocks inheritance
and indents).
prev parent reply other threads:[~2017-10-12 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 14:40 Cristian Dumitrescu
2017-10-12 17:10 ` 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=3569007.OBp7ulgCO0@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
/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).