patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
	dpdk stable <stable@dpdk.org>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Trahe, Fiona" <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>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"Yao, Lei A" <lei.a.yao@intel.com>,
	Matan Azrad <matan@mellanox.com>,
	Nelio 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>,
	"Bie, Tiwei" <tiwei.bie@intel.com>,
	Xueming 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: Thu, 8 Feb 2018 01:53:52 +0000	[thread overview]
Message-ID: <ED26CBA2FAD1BF48A8719AEF02201E3651432F88@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180207191428.14532-1-luca.boccassi@gmail.com>

Hi Luca,

> -----Original Message-----
> From: luca.boccassi@gmail.com [mailto:luca.boccassi@gmail.com]
> Sent: Thursday, February 8, 2018 3:14 AM
> To: dpdk stable
> Cc: Ajit Khaparde; Burakov, Anatoly; Yigit, Ferruh; Trahe, Fiona; Harish Patil;
> Hemant Agrawal; Jerin Jacob; Jia He; Tan, Jianfeng; Ananyev, Konstantin; Yao,
> Lei A; Matan Azrad; Nelio Laranjeiro; Olivier Matz; Rasesh Mody; Santosh
> Shukla; Shahaf Shuler; Thomas Monjalon; Bie, Tiwei; Xueming Li; Yong Wang;
> Yuanhan Liu
> Subject: please help backporting some patches to LTS release 16.11.5
> 
> 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: 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".
> 
> Thanks.
> 
> Luca Boccassi
> 
> ---
> dbcabb69e  Ajit Khaparde    net/bnxt: fix number of pools for RSS
> 14ec04e1a  Anatoly Burakov  test/ring: fix memory leak
> dd28bc8c6  Harish Patil     net/qede: fix VF port creation sequence
> 96fd032ba  Hemant Agrawal   eal: prefix mbuf pool ops name with user
> defined
> 59a3cae53  Jia He           eal/arm64: remove the braces in memory barrier
> macros
> 0d6a8752a  Jianfeng Tan     net/virtio-user: fix crash as features change

We don't have to back-port the above fix if below commit is not back-ported.
commit 59fe5e17d930 ("vhost: propagate set features handling error")

Thanks,
Jianfeng

> 133b54779  Matan Azrad      ethdev: fix port data reset timing
> 8ee892a23  Matan Azrad      ethdev: fix port id allocation
> ce26be6ed  Rasesh Mody      net/qede: fix clearing of queue stats
> 9e3343051  Rasesh Mody      net/qede: fix MTU set and max Rx length
> e313ef4c2  Shahaf Shuler    net/mlx5: fix link state on device start
> 2ab9a9483  Thomas Monjalon  crypto/dpaa2_sec: fix build with GCC 7
> 0bf876008  Xueming Li       cmdline: avoid garbage in unused fields of parsed
> result
> 2acf7432a  Xueming Li       cmdline: fix dynamic tokens parsing
> 963898f0e  Yong Wang        crypto/qat: fix allocation check and leak

  reply	other threads:[~2018-02-08  1:53 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 [this message]
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
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=ED26CBA2FAD1BF48A8719AEF02201E3651432F88@SHSMSX103.ccr.corp.intel.com \
    --to=jianfeng.tan@intel.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=konstantin.ananyev@intel.com \
    --cc=lei.a.yao@intel.com \
    --cc=luca.boccassi@gmail.com \
    --cc=matan@mellanox.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).