patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: dpdk stable <stable@dpdk.org>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Anatoly Burakov <anatoly.burakov@intel.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Dmitri Epshtein <dima@marvell.com>, Gavin Hu <gavin.hu@arm.com>,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	Jananee Parthasarathy <jananeex.m.parthasarathy@intel.com>,
	Jan Viktorin <viktorin@rehivetech.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Jianbo Liu <jianbo.liu@arm.com>, Matan Azrad <matan@mellanox.com>,
	Moti Haimovsky <motih@mellanox.com>,
	Natalie Samsonov <nsamsono@marvell.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Rasesh Mody <rasesh.mody@cavium.com>,
	Remy Horton <remy.horton@intel.com>,
	Reshma Pattan <reshma.pattan@intel.com>,
	Song Zhu <song.zhu@arm.com>, Tomasz Duszynski <tdu@semihalf.com>
Subject: [dpdk-stable] please help backporting some patches to LTS release 17.11.4
Date: Mon, 13 Aug 2018 13:45:44 -0700	[thread overview]
Message-ID: <20180813204544.25762-1-yskoh@mellanox.com> (raw)

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

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

---
22dcd9a4d  Anatoly Burakov  test: parallelize unit tests
33310b592  Beilei Xing      net/i40e: fix device parameter parsing
94110dc0d  Gavin Hu         maintainers: claim maintainership for ARM v7 and v8
9eabcb682  Jananee Parthasarathy test: update autotest list
4278f8df4  Matan Azrad      net/tap: fix zeroed flow mask configurations
ff9fe66c9  Moti Haimovsky   net/mlx4: advertise Rx jumbo frame support
2b4e423fd  Moti Haimovsky   net/mlx4: check RSS queues number limitation
c8dbf6814  Rasesh Mody      net/qede/base: fix to clear HW indication
8224b9d68  Reshma Pattan    latency: free up the memzone

             reply	other threads:[~2018-08-13 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 20:45 Yongseok Koh [this message]
     [not found] <CGME20180727024051epcas3p20e5aa80ae259e6d8d83d44d60fd32625@epcas3p2.samsung.com>
2018-07-27  2:40 ` Yongseok Koh
2018-07-27  7:42   ` Ilya Maximets
2018-07-27  9:23     ` Luca Boccassi
2018-07-27 16:25     ` Kevin Traynor
2018-07-27 16:46       ` Ilya Maximets
2018-07-27 17:24         ` Kevin Traynor
2018-07-27 17:32           ` Yongseok Koh
2018-07-29  5:59   ` Shahaf Shuler

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=20180813204544.25762-1-yskoh@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=anatoly.burakov@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dima@marvell.com \
    --cc=gavin.hu@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jananeex.m.parthasarathy@intel.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=jianbo.liu@arm.com \
    --cc=matan@mellanox.com \
    --cc=motih@mellanox.com \
    --cc=nsamsono@marvell.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rasesh.mody@cavium.com \
    --cc=remy.horton@intel.com \
    --cc=reshma.pattan@intel.com \
    --cc=song.zhu@arm.com \
    --cc=stable@dpdk.org \
    --cc=tdu@semihalf.com \
    --cc=viktorin@rehivetech.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).