From: Matan Azrad <matan@mellanox.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
dpdk stable <stable@dpdk.org>
Cc: "Ajit Khaparde" <ajit.khaparde@broadcom.com>,
"Anatoly Burakov" <anatoly.burakov@intel.com>,
"Ferruh Yigit" <ferruh.yigit@intel.com>,
"Fiona Trahe" <fiona.trahe@intel.com>,
"Harish Patil" <harish.patil@cavium.com>,
"Hemant Agrawal" <hemant.agrawal@nxp.com>,
"Jerin Jacob" <jerin.jacob@caviumnetworks.com>,
"Jia He" <jia.he@hxt-semitech.com>,
"Jianfeng Tan" <jianfeng.tan@intel.com>,
"Konstantin Ananyev" <konstantin.ananyev@intel.com>,
"Lei Yao" <lei.a.yao@intel.com>,
"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Olivier Matz" <olivier.matz@6wind.com>,
"Rasesh Mody" <rasesh.mody@cavium.com>,
"Santosh Shukla" <santosh.shukla@caviumnetworks.com>,
"Shahaf Shuler" <shahafs@mellanox.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Tiwei Bie" <tiwei.bie@intel.com>,
"Xueming(Steven) Li" <xuemingl@mellanox.com>,
"Yong Wang" <wang.yong19@zte.com.cn>,
"Yuanhan Liu" <yliu@fridaylinux.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.5
Date: Sun, 11 Feb 2018 07:49:15 +0000 [thread overview]
Message-ID: <AM4PR0501MB26571E9C8A22522F45C3C654D2F00@AM4PR0501MB2657.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180207191428.14532-1-luca.boccassi@gmail.com>
Hi Luca
From: luca.boccassi@gmail.com, Sent: Wednesday, February 7, 2018 9:14 PM
> Hi commit authors (and maintainers),
>
> I didn't manage to apply following commits from upstream to stable branch
> 16.11: conflict happens. I'm wondering can the authors check the following
> list and backport those patches belong to you?
>
> FYI, branch 16.11 is located at tree:
> git://dpdk.org/dpdk-stable
>
> It'd be great if you could do that in one or two weeks. Also, please add a
> heading line like below before the commit log body:
> [ backported from upstream commit xxx ]
>
> Example:
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpd
> k.org%2Fbrowse%2Fdpdk-
> stable%2Fcommit%2F%3Fh%3D16.07%26id%3Dc4831394c7d1944d8ec27d52c2
> 2997f20d19718e&data=02%7C01%7Cmatan%40mellanox.com%7Cbe758d6ff1
> d1410db8da08d56e5f0db0%7C8c5c71989dbe4cf9a2099e499881116c%7C0%7C
> 0%7C636536276909341667&sdata=rvd%2FFaic781qiftZmojqZSwGBSHqVqa1%
> 2BxQo8cKPG2s%3D&reserved=0
>
> 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".
>
> Thanks.
>
> Luca Boccassi
>
> ---
> 133b54779 Matan Azrad ethdev: fix port data reset timing
> 8ee892a23 Matan Azrad ethdev: fix port id allocation
I think these 2 fixes are not relevant to 16.11 version.
Matan.
next prev parent reply other threads:[~2018-02-11 7:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 13:30 luca.boccassi
2018-01-26 18:26 ` Yongseok Koh
2018-01-26 18:40 ` Luca Boccassi
2018-01-28 5:47 ` Matan Azrad
2018-01-28 14:17 ` Luca Boccassi
2018-01-30 14:26 ` Nélio Laranjeiro
2018-01-30 14:36 ` Luca Boccassi
2018-02-02 20:05 ` [dpdk-stable] [PATCH 0/2] bnxt patchset for 16.11 Ajit Khaparde
2018-02-02 20:05 ` [dpdk-stable] [PATCH 1/2] net/bnxt: fix group info usage Ajit Khaparde
2018-02-02 20:05 ` [dpdk-stable] [PATCH 2/2] net/bnxt: fix broadcast cofiguration Ajit Khaparde
2018-02-05 13:46 ` [dpdk-stable] [PATCH 0/2] bnxt patchset for 16.11 Luca Boccassi
2018-02-07 19:14 ` [dpdk-stable] please help backporting some patches to LTS release 16.11.5 luca.boccassi
2018-02-08 1:53 ` Tan, Jianfeng
2018-02-08 10:37 ` Luca Boccassi
2018-02-08 21:47 ` Ajit Khaparde
2018-02-08 22:31 ` Luca Boccassi
2018-02-11 7:49 ` Matan Azrad [this message]
2018-02-11 11:26 ` Luca Boccassi
2018-02-14 8:46 ` Olivier Matz
2018-02-14 10:16 ` Luca Boccassi
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=AM4PR0501MB26571E9C8A22522F45C3C654D2F00@AM4PR0501MB2657.eurprd05.prod.outlook.com \
--to=matan@mellanox.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anatoly.burakov@intel.com \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=harish.patil@cavium.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jia.he@hxt-semitech.com \
--cc=jianfeng.tan@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=lei.a.yao@intel.com \
--cc=luca.boccassi@gmail.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=olivier.matz@6wind.com \
--cc=rasesh.mody@cavium.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=shahafs@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tiwei.bie@intel.com \
--cc=wang.yong19@zte.com.cn \
--cc=xuemingl@mellanox.com \
--cc=yliu@fridaylinux.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).