From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: dev <dev@dpdk.org>, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] Suggestions for the dpdk stable tree
Date: Fri, 20 May 2016 10:07:13 +0200 [thread overview]
Message-ID: <CAATJJ0L6RH-BCsi8fgwAcje4HhLU=DfXkbTDk5NtaEBh3ez16Q@mail.gmail.com> (raw)
In-Reply-To: <CAATJJ0JjnhPhDdG8r5nLb5g40xchetPto7CdW=E-xBfR0vHbdw@mail.gmail.com>
Hi,
I guess over time/releases less people mind the 2.2-stable.
But I still see a lot of people referring to 2.2 - so why not giving this
thread a ping again.
ack / nack / opinions ?
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
On Thu, Mar 24, 2016 at 8:14 AM, Christian Ehrhardt <
christian.ehrhardt@canonical.com> wrote:
> Hi,
> there is a stable tree for dpdk 2.2 at http://dpdk.org/browse/dpdk-stable/
> But it is still at the 2.2 Release status.
>
> I was working on testing 2.2 and needed to pull in some patches from post
> 2.2 release to fix issues.
> After that I started to "scan" the git log what else might apply to a
> clean and uncritical addition to a dpdp-2.2 as "stability backports".
>
> I had a focus on identifying:
> - only patches to components that are enabled in our packaging (well that
> is close to the default conf so it should be ok for you as well)
> - issues that have a real chance to occur
> - patches that are small, so review is not overly complex
> - apply without manual adaption (offset ok to some extend, no fuzz, no
> manual fix)
> I realized that I should suggest that list of patches to you to consider
> adding it to the stable tree.
> So therefore for you to consider:
>
>
> commit d3a274ce9dee28118b8647e0db72ef0f4b6a6323
>
> app/testpmd: handle SIGINT and SIGTERM
>
> commit 308df2bfba3d238fc1d2d16cc10c84681803b408
>
> Handle SIGINT and SIGTERM in l3fwd.
>
> commit da82ee17e6ea99bf2931383ac33b0caccaaaefce
>
> tools: fix unbinding failure handling
>
> commit 16c1814c802c205f6d3c32e3d3d10de9f87e7f22
>
> tools: support Python 3 in bind script
>
> commit bb9f408550d13af6c1da104b0d9d9b9837f69bde
>
> tools: support binding to built-in kernel modules
>
>
> commit 6e7caa1ad9d597fed0a49468af25ae6e68b8c443
>
> eal/linux: support built-in kernel modules
>
>
> commit 86f36ff9578b5f3d697c8fcf6072dcb70e2b246f
>
> mempool: fix leak when creation fails
>
>
> commit ca67ed289a76f38d6c4a4021985a36eaf1d77e28
>
> vhost: fix leak of fds and mmaps
>
>
> commit fa11a8a7251e14eca0a4190128732386f13551bd
>
> port: fix crash for ring writer nodrop
>
> commit 04f366906ab395c8047bebfc1ddea244dfcb40f5
>
> port: fix crash for ethdev writer nodrop
>
>
> commit c7a4ff80722e9237a4c504106d21ba5ca27d8df2
>
> i40e: fix overflow
>
> commit 097e920c32bf19cf918cc071525f33b0abdeebaf
>
> i40e: fix inverted check for no refcount
>
> commit 330aa319382aec9ea595f9ebcb9a3c44647ad66c
>
> i40e: fix VLAN filtering
>
> commit 9f44dd3d8ad447c7f797a9564d30a15e5ab7f72b
>
> i40e/base: fix missing check for stopped admin queue
>
> commit 8a8807369ffafef90c410279b4b2645d2d7a7483
>
> i40e/base: fix driver load failure
>
>
> commit 7656a546c0609f3205558a5d48352c82607d38d3
>
> fm10k: fix VLAN flag in scattered Rx
>
>
> commit c6fb0e55585206a89f6db396de860e6e844cad06
>
> pcap: fix captured frame length
>
>
> commit 6e02723754fb2b341701ac438486b2dfea98b523
>
> bonding: fix detach of bonded device
>
> commit df3e8ad73f4c92b4eb8f49ff33271d4a09e6a04a
>
> bonding: fix detach of slave devices
>
> commit 786c990a11e6e6592dfdee02840877070aa3a79a
>
> bonding: copy entire config structure in mode 4
>
> commit 6698820b5f6d955b6af2b916e1074db236d4f5a2
>
> bonding: do not ignore multicast in mode 4
>
> commit 8997a10bfcad789d000debaac4cd85cd3db57997
>
> bonding: fix active slaves with no primary
>
> commit 7a7122edf1c8d63e516d1b2c2eff6fa9b54e0f82
>
> bonding: do not activate slave twice
>
> commit 2186fff3675d4e774cecc8f918c05063e0367d28
>
> bonding: fix crash when no slave device
>
>
> commit 3b1e3e4e362453df8cecbc6d481444be8b84326e
>
> virtio: fix descriptors pointing to the same buffer
>
> commit c680a4a88c4312068f60937a7ba51eac8211c9a6
>
> virtio: fix crash in statistics functions
>
> commit 9a0615af7746485d73d10561cc0743bc2fcd4bf7
>
> virtio: fix restart
>
>
> Christian Ehrhardt
> Software Engineer, Ubuntu Server
> Canonical Ltd
>
next prev parent reply other threads:[~2016-05-20 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 7:14 Christian Ehrhardt
2016-05-20 8:07 ` Christian Ehrhardt [this message]
2016-05-20 14:49 ` Mcnamara, John
2016-05-20 15:54 ` Christian Ehrhardt
2016-05-20 21:02 ` Markos Chandras
2016-05-23 2:21 ` Yuanhan Liu
2016-06-01 19:01 ` Mcnamara, John
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='CAATJJ0L6RH-BCsi8fgwAcje4HhLU=DfXkbTDk5NtaEBh3ez16Q@mail.gmail.com' \
--to=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).