From: <wang.yong19@zte.com.cn>
To: <yliu@fridaylinux.org>
Cc: <stable@dpdk.org>, <anatoly.burakov@intel.com>,
<beilei.xing@intel.com>, <bernard.iremonger@intel.com>,
<harish.patil@cavium.com>, <nelio.laranjeiro@6wind.com>,
<olivier.matz@6wind.com>, <ophirmu@mellanox.com>,
<pbhagavatula@caviumnetworks.com>, <qi.z.zhang@intel.com>,
<shahafs@mellanox.com>, <vipin.varghese@intel.com>,
<yskoh@mellanox.com>
Subject: [dpdk-stable] 答复: please help backporting some patches to LTS release 17.11.1
Date: Thu, 8 Feb 2018 15:44:34 +0800 (CST) [thread overview]
Message-ID: <201802081544348835371@zte.com.cn> (raw)
In-Reply-To: <20180207093155.GA31542@yliu-mob>
I can't get the code from git. The error occured is below. What should I do now?
[root@localhost 2017]# git clone git://dpdk.org/dpdk-stable
Cloning into 'dpdk-stable'...
fatal: unable to connect to dpdk.org:
dpdk.org[0: 92.243.14.124]: errno=Connection timed out
[root@localhost 2017]# git clone http://dpdk.org/dpdk-stable
Cloning into 'dpdk-stable'...
fatal: repository 'http://dpdk.org/dpdk-stable/' not found
------------------origin------------------
send:YuanhanLiu <yliu@fridaylinux.org>
to:dpdk stable <stable@dpdk.org>
cc:Anatoly Burakov <anatoly.burakov@intel.com>Beilei Xing <beilei.xing@intel.com>Bernard Iremonger <bernard.iremonger@intel.com>Harish Patil <harish.patil@cavium.com>Nelio Laranjeiro <nelio.laranjeiro@6wind.com>Olivier Matz <olivier.matz@6wind.com>Ophir Munk <ophirmu@mellanox.com>Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>Qi Zhang <qi.z.zhang@intel.com>Shahaf Shuler <shahafs@mellanox.com>Vipin Varghese <vipin.varghese@intel.com>Yongseok Koh <yskoh@mellanox.com>汪勇10032886;
date :2018年02月07日 17:32
subject :please help backporting some patches to LTS release 17.11.1
Hi commit authors (and maintainers),
I didn't manage to apply following commits from upstream to stable branch
17.11: conflict happens. I'm wondering can the authors check the following
list and backport those patches belong to you?
FYI, branch 17.11 is located at tree:
git://dpdk.org/dpdk-stable
It'd be great if you could do that in one weeks. Also, please add a
heading line like below before the commit log body:
[ backported from upstream commit xxx ]
Example: http://dpdk.org/browse/dpdk-stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e
Please let me know if you have any comments, say, need more time, or it's
worthless to packport it. And please send it to "stable@dpdk.org", but not
"dev@dpdk.org".
Also, please make an reply to me when you have done that, just in case I
may miss the backport email.
Thanks.
-yliu
---
5c45e0f Anatoly Burakov test/memzone: handle previously allocated memzones
4ab8314 Beilei Xing net/i40e: fix interrupt conflict with multi-driver
cfdfca4 Beilei Xing net/i40e: fix multiple driver support
378cc7f Beilei Xing net/i40e: fix Rx interrupt
5cbf8b4 Bernard Iremonger test/flow_classify: remove port bound requirement
dd28bc8 Harish Patil net/qede: fix VF port creation sequence
c3299d7 Nélio Laranjeiro net/mlx5: fix flow priority on queue action
f07f9bc Nélio Laranjeiro net/mlx5: fix port stop by verify flows are still present
51e7fa8 Nélio Laranjeiro net/mlx5: fix secondary process verification
35906ac Olivier Matz net/bnxt: fix headroom initialization
70205b5 Ophir Munk net/failsafe: fix default Tx offloads capabilities
452cd79 Pavan Nikhilesh app/eventdev: fix event device queue count
dd18b06 Qi Zhang net/e1000: fix mailbox interrupt handler
6810c63 Qi Zhang net/ixgbe: fix mailbox interrupt handler
cd230a3 Shahaf Shuler net/mlx5: fix CRC strip capability query
e313ef4 Shahaf Shuler net/mlx5: fix link state on device start
da23f0a Vipin Varghese service: fix memory leak with new function
c7bf622 Yongseok Koh net/mlx5: fix handling link status event
0ff7683 Yong Wang net/dpaa: fix potential memory leak
next prev parent reply other threads:[~2018-02-08 7:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 9:31 [dpdk-stable] " Yuanhan Liu
2018-02-08 7:44 ` wang.yong19 [this message]
2018-02-08 8:46 ` Pavan Nikhilesh
2018-02-08 8:56 ` Yuanhan Liu
2018-02-11 4:54 ` Yuanhan Liu
2018-02-12 10:36 ` Burakov, Anatoly
2018-02-13 11:46 ` Yuanhan Liu
2018-02-13 11:49 ` Burakov, Anatoly
2018-02-20 11:02 ` Burakov, Anatoly
2019-03-06 10:56 ` Burakov, Anatoly
2019-03-06 19:03 ` Yongseok Koh
2019-03-07 12:04 ` Burakov, Anatoly
2019-03-07 20:10 ` Yongseok Koh
2018-02-14 8:58 ` [dpdk-stable] [PATCH 1/3] net/mlx5: fix secondary process verification Nelio Laranjeiro
2018-02-16 13:01 ` Yuanhan Liu
2018-02-14 8:58 ` [dpdk-stable] [PATCH 2/3] net/mlx5: fix port stop by verify flows are still present Nelio Laranjeiro
2018-02-14 8:58 ` [dpdk-stable] [PATCH 3/3] net/mlx5: fix flow priority on queue action Nelio Laranjeiro
2018-02-27 9:36 ` [dpdk-stable] [PATCH 1/3] Revert "net/mlx5: fix flow priority on queue action" Nelio Laranjeiro
2018-02-27 9:49 ` Yuanhan Liu
2018-02-27 9:36 ` [dpdk-stable] [PATCH 2/3] net/mlx5: remove parser/flow drop queue Nelio Laranjeiro
2018-02-27 9:36 ` [dpdk-stable] [PATCH 3/3] net/mlx5: fix flow priority on queue action Nelio Laranjeiro
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=201802081544348835371@zte.com.cn \
--to=wang.yong19@zte.com.cn \
--cc=anatoly.burakov@intel.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=harish.patil@cavium.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=olivier.matz@6wind.com \
--cc=ophirmu@mellanox.com \
--cc=pbhagavatula@caviumnetworks.com \
--cc=qi.z.zhang@intel.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=vipin.varghese@intel.com \
--cc=yliu@fridaylinux.org \
--cc=yskoh@mellanox.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).