From: Maciej Czekaj <maciej.czekaj@caviumnetworks.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
dpdk stable <stable@dpdk.org>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Chas Williams <3chas3@gmail.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Harish Patil <harish.patil@qlogic.com>,
Nelson Escobar <neescoba@cisco.com>,
Piotr Azarewicz <piotrx.t.azarewicz@intel.com>
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
John Daley <johndale@cisco.com>,
Kamil Rytarowski <kamil.rytarowski@caviumnetworks.com>,
Michal Jastrzebski <michalx.k.jastrzebski@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Radoslaw Biernacki <rad@semihalf.com>,
Slawomir Rosek <slawomir.rosek@semihalf.com>,
Zyta Szpak <zyta.szpak@semihalf.com>
Subject: Re: [dpdk-stable] request backporting some patches to 16.07.2
Date: Wed, 16 Nov 2016 11:48:58 +0100 [thread overview]
Message-ID: <ed54c033-f73a-bd6f-5151-b21df4229125@caviumnetworks.com> (raw)
In-Reply-To: <20161115135814.GC5048@yliu-dev.sh.intel.com>
Hi,
Excuse me for late response.
I tried to apply the patch
6d3cbd5 Kamil Rytarowski net/thunderx: remove private data to ethdev link
but it strongly depends on previous patches from the whole patchset
submitted to 16.11 so I think it does not make sense to apply that fix
to 16.07.
Thanks
Maciej
On Tue, 15 Nov 2016 21:58:14 +0800 Yuanhan Liu wrote:
> Hi,
>
> I still havn't got any response for following commits. Just want to let
> you know, that if you can make a backport in this week, we could still
> make it in 16.07.2 release.
>
> And please do me a favor by adding a heading line like following before
> the commit log body if you are willing to offer help:
>
> [ backported from upstream commit xxx ]
>
> Thanks.
>
> -yliu
>
> ---
> 6d3cbd5 Kamil Rytarowski net/thunderx: remove private data to ethdev link
> cf32c2e Chas Williams net/bnx2x: serialize access to VF mailbox
> 316e412 Ajit Khaparde net/bnxt: fix crash when closing
> 893fbab Piotr Azarewicz examples/l2fwd-crypto: fix verify with decrypt in chain
> 6445198 Ferruh Yigit kni: fix build with kernel 4.9
> e8a71c4 Nelson Escobar net/enic: fix Rx queue index when not using Rx scatter
> dbac54c Harish Patil net/qede: fix port (re)configuration
> d6cb175 Harish Patil net/qede: fix VLAN filters
> f1e4b6c Harish Patil net/qede: fix status block index for VF queues
>
> On Sun, Nov 06, 2016 at 03:22:13PM +0800, Yuanhan Liu wrote:
>> Hi commit authors (and maintainers),
>>
>> I tried to pick following commits from upstream to stable branch 16.07,
>> but I failed: they can't be applied. I'm wondering can the authors check
>> the list and backport some patches belong to them?
>>
>> FYI, branch 16.07 at git://dpdk.org/dpdk-stable is the place those patches
>> should be packported to. If you are willing to do that, it'd be great if
>> you could do it in one week (or two). Please drop me an email if you are
>> willing to do that, or if you need more time, or even, if you think it's
>> worthless to packport it.
>>
>> Thanks.
>>
>> -yliu
>>
>> ---
>> 10313a4 ethdev: fix vendor id in debug message
>> 243e93a hash: fix unlimited cuckoo path
>> 94eaeba hash: fix bucket size usage
>> 6d3cbd5 net/thunderx: remove private data to ethdev link
>> b16e60a net/enic: document how to configure vNIC parameters
>> cf32c2e net/bnx2x: serialize access to VF mailbox
>> 316e412 net/bnxt: fix crash when closing
>> 893fbab examples/l2fwd-crypto: fix verify with decrypt in chain
>> 6445198 kni: fix build with kernel 4.9
>> e8a71c4 net/enic: fix Rx queue index when not using Rx scatter
>> ceeb00b net/enic: fix crash on MTU update or Rx queue reconfigure
>> ce16fd7 net/enic: fix multi-queue Rx performance
>> ff6edd3 net/i40e: fix out of order Rx read
>> 6949188 net/mlx5: fix initialization in secondary process
>> dbac54c net/qede: fix port (re)configuration
>> d6cb175 net/qede: fix VLAN filters
>> f1e4b6c net/qede: fix status block index for VF queues
>> 75ef62a net/mlx5: fix link speed capability information
>> 1884087 net/mlx5: fix support for newer link speeds
next prev parent reply other threads:[~2016-11-16 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 7:22 Yuanhan Liu
2016-11-15 13:58 ` Yuanhan Liu
2016-11-16 10:48 ` Maciej Czekaj [this message]
2016-11-16 11:57 ` Yuanhan Liu
2016-11-18 12:23 ` [dpdk-stable] [PATCH 1/2] kni: fix build with kernel 4.8 Ferruh Yigit
2016-11-18 12:23 ` [dpdk-stable] [PATCH 2/2] kni: fix build with kernel 4.9 Ferruh Yigit
2016-11-21 6:07 ` [dpdk-stable] [PATCH 1/2] kni: fix build with kernel 4.8 Yuanhan Liu
2016-11-16 16:51 ` [dpdk-stable] request backporting some patches to 16.07.2 Harish Patil
2016-11-16 22:01 ` John Daley (johndale)
2016-11-15 13:29 Yuanhan Liu
2016-11-21 9:38 ` Kusztal, ArkadiuszX
2016-11-21 11:31 ` Yuanhan Liu
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=ed54c033-f73a-bd6f-5151-b21df4229125@caviumnetworks.com \
--to=maciej.czekaj@caviumnetworks.com \
--cc=3chas3@gmail.com \
--cc=ajit.khaparde@broadcom.com \
--cc=ferruh.yigit@intel.com \
--cc=harish.patil@qlogic.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=johndale@cisco.com \
--cc=kamil.rytarowski@caviumnetworks.com \
--cc=michalx.k.jastrzebski@intel.com \
--cc=neescoba@cisco.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=piotrx.t.azarewicz@intel.com \
--cc=rad@semihalf.com \
--cc=slawomir.rosek@semihalf.com \
--cc=stable@dpdk.org \
--cc=yuanhan.liu@linux.intel.com \
--cc=zyta.szpak@semihalf.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).