patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: dpdk stable <stable@dpdk.org>
Cc: Bernard Iremonger <bernard.iremonger@intel.com>,
	Brian Russell <brussell@brocade.com>,
	Geoffrey Lv <geoffrey.lv@gmail.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Luca Boccassi <bluca@debian.org>, Qi Zhang <qi.z.zhang@intel.com>,
	Radu Nicolau <radu.nicolau@intel.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
	Yongseok Koh <yskoh@mellanox.com>
Subject: [dpdk-stable] please help backporting some patches to stable release 18.08.1
Date: Fri, 23 Nov 2018 10:51:04 +0000	[thread overview]
Message-ID: <20181123105104.18465-1-ktraynor@redhat.com> (raw)

Hi commit authors (and maintainers),

I didn't manage to apply or compile following commits from upstream to stable
branch 18.08: conflict happens. I'm wondering can the authors check the following
list and backport those patches belong to you?

FYI, branch 18.08 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 stable in the subject line, as we have more than one
at the same time, for example:

    [PATCH 18.08] foo/bar: fix baz

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

    --subject-prefix='18.08'

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.

Kevin Traynor

---
Didn't compile:
5d08fecdd  Jerin Jacob      eal: fix build
beb5477f4  Luca Boccassi    net/vmxnet3: fix hot-unplug
d8e4dc751  Qi Zhang         bus/pci: fix resource mapping override
baea19359  Radu Nicolau     app/testpmd: fix port status for new bonded devices

Didn't apply:
84be903c0  Viacheslav Ovsiienko net/mlx5: fix flow counters deletion in Verbs
2720f833d  Yongseok Koh     net/mlx5: add missing flow director delete

             reply	other threads:[~2018-11-23 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 10:51 Kevin Traynor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-29 13:56 Kevin Traynor
2018-11-22 17:46 Kevin Traynor

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=20181123105104.18465-1-ktraynor@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bernard.iremonger@intel.com \
    --cc=bluca@debian.org \
    --cc=brussell@brocade.com \
    --cc=geoffrey.lv@gmail.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=qi.z.zhang@intel.com \
    --cc=radu.nicolau@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@mellanox.com \
    --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).