patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: dpdk stable <stable@dpdk.org>
Cc: Akhil Goyal <akhil.goyal@nxp.com>,
	Anoob Joseph <anoob.joseph@caviumnetworks.com>,
	Archana Muniganti <muniganti.archana@caviumnetworks.com>,
	Chao Zhu <chaozhu@linux.vnet.ibm.com>,
	David Wilder <dwilder@us.ibm.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Geoffrey Lv <geoffrey.lv@gmail.com>,
	Ilya Maximets <i.maximets@samsung.com>,
	Jasvinder Singh <jasvinder.singh@intel.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Junxiao Shi <git@mail1.yoursunny.com>,
	Keith Wiles <keith.wiles@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Nikhil Rao <nikhil.rao@intel.com>,
	Pradeep Satyanarayana <pradeep@us.ibm.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Rasesh Mody <rasesh.mody@cavium.com>,
	Raslan Darawsheh <rasland@mellanox.com>,
	Rosen Xu <rosen.xu@intel.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	Tiwei Bie <tiwei.bie@intel.com>
Subject: [dpdk-stable] please help backporting some patches to LTS release 17.11.5
Date: Fri, 11 Jan 2019 02:43:55 -0800	[thread overview]
Message-ID: <20190111104355.21617-1-yskoh@mellanox.com> (raw)

Hi commit authors (and maintainers),

For some reason, there are 36 missing patches from upstream (up to 18.11). I
could apply 19 patches but I could not apply following patches from upstream to
stable/17.11. Can you please check the following list and backport those
patches?

FYI, branch 17.11 is located at tree:
   git://dpdk.org/dpdk-stable

It'd be great if you could do that in one week as I will release RC2 soon. Also,
please add a 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

Also please mention the target LTS in the subject line, as we have more than one
at the same time, for example:

    [PATCH 17.11] foo/bar: fix baz

With git send-email, this can be achieved by appending the parameter:

    --subject-prefix='17.11'

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,
Yongseok

---
2e960c97c  Anoob Joseph     examples/ipsec-secgw: fix wrong session size
6b062d56b  David Wilder     mem: fix anonymous mapping on Power9
66cdfd67c  Jasvinder Singh  net/softnic: fix undefined device info fields
13ffe6059  Jerin Jacob      doc: clarify VLAN and QinQ Tx offload prerequisite
f49d7e9a9  Junxiao Shi      cryptodev: fix pool element size for undefined operation
74ee315e4  Maxime Coquelin  vhost: fix error handling when mem table gets updated
d7b5f102c  Nikhil Rao       eventdev: fix eth Rx adapter hotplug incompatibility
475425186  Nikhil Rao       eventdev: fix port id argument in Rx adapter caps
e846cfdec  Nikhil Rao       eventdev: fix unlock in Rx adapter
55e411b30  Qi Zhang         bus/pci: fix resource mapping override
d5df6159d  Rasesh Mody      net/qede: fix ethernet type in HW registers
9396ad334  Raslan Darawsheh net/tap: fix reported number of Tx packets
c2c15f769  Rosen Xu         app/testpmd: fix shaper profile parameters
c1752a36b  Sachin Saxena    net/dpaa: fix link speed based on MAC type
6bdf14455  Thomas Monjalon  eal/x86: remove unused memcpy file
66908eff1  Tiwei Bie        net/virtio: add missing supported features
f457e9007  Tiwei Bie        net/virtio-user: do not stop stopped device again

             reply	other threads:[~2019-01-11 10:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 10:43 Yongseok Koh [this message]
2019-01-11 11:49 ` yoursunny
2019-01-11 22:43   ` Yongseok Koh
2019-01-12 11:46 ` Anoob Joseph
2019-01-15  8:31   ` Akhil Goyal
2019-01-15 16:42     ` Yongseok Koh
     [not found] ` <54CBAA185211B4429112C315DA58FF6D3369EBA7@IRSMSX103.ger.corp.intel.com>
2019-01-14 19:37   ` Yongseok Koh
2019-01-17  0:13 ` dwilder
  -- strict thread matches above, loose matches on Subject: below --
2018-11-29 23:43 Yongseok Koh
2018-11-30  1:40 ` yoursunny
2018-11-30  8:01   ` Yongseok Koh
2018-12-01  0:32 ` dwilder
2018-12-05 19:02   ` Yongseok Koh
2018-12-14  4:34 ` Cao, Yahui
2018-12-14  7:55   ` Yongseok Koh
2018-12-18  8:36 ` Cao, Yahui
2018-12-19 20:00   ` Yongseok Koh
     [not found] ` <BYAPR18MB28389793C29112B573D875ADB5840@BYAPR18MB2838.namprd18.prod.outlook.com>
2019-01-11  9:55   ` Yongseok Koh

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=20190111104355.21617-1-yskoh@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoob.joseph@caviumnetworks.com \
    --cc=chaozhu@linux.vnet.ibm.com \
    --cc=dwilder@us.ibm.com \
    --cc=ferruh.yigit@intel.com \
    --cc=geoffrey.lv@gmail.com \
    --cc=git@mail1.yoursunny.com \
    --cc=i.maximets@samsung.com \
    --cc=jasvinder.singh@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=keith.wiles@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=muniganti.archana@caviumnetworks.com \
    --cc=nikhil.rao@intel.com \
    --cc=pradeep@us.ibm.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rasesh.mody@cavium.com \
    --cc=rasland@mellanox.com \
    --cc=rosen.xu@intel.com \
    --cc=sachin.saxena@nxp.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=tiwei.bie@intel.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).