patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yongseok Koh <yskoh@mellanox.com>
To: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>
Cc: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
	"Shahaf Shuler" <shahafs@mellanox.com>,
	"dpdk stable" <stable@dpdk.org>
Subject: Re: [dpdk-stable] please help backporting some patches to LTS release 16.11.5
Date: Fri, 26 Jan 2018 18:26:28 +0000	[thread overview]
Message-ID: <7876B62D-CE1C-4FDD-B698-8C56C5B71E1E@mellanox.com> (raw)
In-Reply-To: <20180126133039.21641-1-luca.boccassi@gmail.com>

> On Jan 26, 2018, at 5:30 AM, luca.boccassi@gmail.com wrote:
> 
> 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?
[...]
> c7bf62255  Yongseok Koh     net/mlx5: fix handling link status event

I don't think it's worth back-porting this patch to 16.11.
The bug was very minor but changes are big.
And in 16.11, it doesn't even have priv_dev_traffic_enable/disable(), which
means this patch could bring another instability.

Please drop the patch for 16.11.5

Thanks
Yongseok

  reply	other threads:[~2018-01-26 18:26 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 [this message]
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
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=7876B62D-CE1C-4FDD-B698-8C56C5B71E1E@mellanox.com \
    --to=yskoh@mellanox.com \
    --cc=luca.boccassi@gmail.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=shahafs@mellanox.com \
    --cc=stable@dpdk.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).