From: Liming Sun <lsun@ezchip.com>
To: "sys_stv@intel.com" <sys_stv@intel.com>,
"test-report@dpdk.org" <test-report@dpdk.org>
Subject: Re: [dpdk-test-report] [PatchWork]|ERROR| pw9781-9782 driver/net/mpipe: add rte_vect.h and enable CONFIG_RTE_LIBRTE_LPM
Date: Fri, 5 Feb 2016 19:27:05 +0000 [thread overview]
Message-ID: <DB5PR02MB1015B4A6E74D936E6BC6BFFABCD20@DB5PR02MB1015.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <2d8c1b$qn70id@fmsmga001.fm.intel.com>
Hi, the following 5 commits were re-submitted on the same day. But can we apply 3/1~3/3 first, then 2/1 ~ 2/2 (due to dependency on the first 3 commits) ?
[dpdk-dev,v2,2/2] driver/net/mpipe: fix the crash/hung issue when testpmd quits 2016-01-08 Liming Sun bruce New
[dpdk-dev,v2,1/2] driver/net/mpipe: add rte_vect.h and enable CONFIG_RTE_LIBRTE_LPM 2016-01-08 Liming Sun bruce New
[dpdk-dev,v2,3/3] driver/net/mpipe: fix a mpipe link initialization ordering issue 2016-01-08 Liming Sun bruce New
[dpdk-dev,v2,2/3] driver/net/mpipe: optimize mpipe buffer return mechanism. 2016-01-08 Liming Sun bruce New
[dpdk-dev,v2,1/3] driver/net/mpipe: support native build on tilegx platform. 2016-01-08 Liming Sun bruce New
I tried locally to merge the commits in the above order based on git baseline 3b60ce8cbb959d7a6839f94ad995a3594c07801e. It appeared working well.
Thanks!
Liming
________________________________________
From: sys_stv@intel.com <sys_stv@intel.com>
Sent: Thursday, February 4, 2016 10:00 PM
To: Liming Sun; test-report@dpdk.org
Subject: [PatchWork]|ERROR| pw9781-9782 driver/net/mpipe: add rte_vect.h and enable CONFIG_RTE_LIBRTE_LPM
Test-Label: Intel Niantic on Fedora
Test-Status: Not run
Patchwork ID: 9781-9782
http://www.dpdk.org/dev/patchwork/patch/9782/
Submitter: Liming Sun <lsun@ezchip.com>
Date: Fri, 8 Jan 2016 09:39:07 -0500
DPDK git baseline: 3b60ce8cbb959d7a6839f94ad995a3594c07801e
9782:
patching file drivers/net/mpipe/mpipe_tilegx.c Hunk #1 succeeded at 127 (offset -7 lines).
Hunk #2 succeeded at 513 (offset -15 lines).
Hunk #3 succeeded at 522 (offset -15 lines).
Hunk #4 succeeded at 543 (offset -15 lines).
Hunk #5 succeeded at 1231 (offset -8 lines).
Hunk #6 FAILED at 1324.
1 out of 6 hunks FAILED -- saving rejects to file drivers/net/mpipe/mpipe_tilegx.c.rej
patching file lib/librte_eal/common/include/arch/tile/rte_rwlock.h
DPDK STV team
prev parent reply other threads:[~2016-02-05 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 3:00 sys_stv
2016-02-05 19:27 ` Liming Sun [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=DB5PR02MB1015B4A6E74D936E6BC6BFFABCD20@DB5PR02MB1015.eurprd02.prod.outlook.com \
--to=lsun@ezchip.com \
--cc=sys_stv@intel.com \
--cc=test-report@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).