patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Thomas Monjalon <thomas@monjalon.net>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 18.02 0/4] ethdev: fix iterator and probing notification
Date: Mon, 21 May 2018 10:46:09 +0100	[thread overview]
Message-ID: <1526895969.23337.143.camel@debian.org> (raw)
In-Reply-To: <20180520110006.9026-1-thomas@monjalon.net>

On Sun, 2018-05-20 at 13:00 +0200, Thomas Monjalon wrote:
> These are the remaining patches from the series
>   "ethdev: fix race conditions in iterator and notifications"
> which were not yet backported in 18.02.
> 
> Please move the commit "net/failsafe: fix sub-device ownership race",
> which was already backported in 18.02 branch,
> on top of these patches, as there is a dependency on notification
> fix.
> Thanks
> 
> 
> Matan Azrad (1):
>   ethdev: allow ownership operations on unused port
> 
> Thomas Monjalon (3):
>   ethdev: add probing finish function
>   ethdev: fix port visibility before initialization
>   ethdev: fix port probing notification
> 
>  drivers/net/af_packet/rte_eth_af_packet.c |  1 +
>  drivers/net/ark/ark_ethdev.c              |  2 ++
>  drivers/net/bonding/rte_eth_bond_pmd.c    |  1 +
>  drivers/net/cxgbe/cxgbe_ethdev.c          |  1 +
>  drivers/net/cxgbe/cxgbe_main.c            |  5 +++
>  drivers/net/dpaa/dpaa_ethdev.c            |  5 ++-
>  drivers/net/dpaa2/dpaa2_ethdev.c          |  4 ++-
>  drivers/net/failsafe/failsafe.c           |  1 +
>  drivers/net/kni/rte_eth_kni.c             |  1 +
>  drivers/net/mlx4/mlx4.c                   |  1 +
>  drivers/net/mlx5/mlx5.c                   |  2 ++
>  drivers/net/mrvl/mrvl_ethdev.c            |  1 +
>  drivers/net/nfp/nfp_net.c                 |  2 ++
>  drivers/net/null/rte_eth_null.c           |  1 +
>  drivers/net/octeontx/octeontx_ethdev.c    |  2 ++
>  drivers/net/pcap/rte_eth_pcap.c           |  1 +
>  drivers/net/ring/rte_eth_ring.c           |  1 +
>  drivers/net/softnic/rte_eth_softnic.c     |  2 ++
>  drivers/net/tap/rte_eth_tap.c             |  1 +
>  drivers/net/vhost/rte_eth_vhost.c         |  1 +
>  drivers/net/virtio/virtio_user_ethdev.c   |  3 ++
>  lib/librte_ether/rte_ethdev.c             | 57 ++++++++++++++++++++-
> ----------
>  lib/librte_ether/rte_ethdev_driver.h      | 14 ++++++++
>  lib/librte_ether/rte_ethdev_pci.h         |  2 ++
>  lib/librte_ether/rte_ethdev_version.map   |  1 +
>  test/test/virtual_pmd.c                   |  2 ++
>  26 files changed, 94 insertions(+), 21 deletions(-)

Thanks, applied and pushed to dpdk-stable/18.02 with minor correction
to the first patch (build issue)

-- 
Kind regards,
Luca Boccassi

      parent reply	other threads:[~2018-05-21  9:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-20 11:00 Thomas Monjalon
2018-05-20 11:00 ` [dpdk-stable] [PATCH 18.02 1/4] ethdev: add probing finish function Thomas Monjalon
2018-05-20 11:00 ` [dpdk-stable] [PATCH 18.02 2/4] ethdev: allow ownership operations on unused port Thomas Monjalon
2018-05-20 11:00 ` [dpdk-stable] [PATCH 18.02 3/4] ethdev: fix port visibility before initialization Thomas Monjalon
2018-05-20 11:00 ` [dpdk-stable] [PATCH 18.02 4/4] ethdev: fix port probing notification Thomas Monjalon
2018-05-21  9:46 ` Luca Boccassi [this message]

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=1526895969.23337.143.camel@debian.org \
    --to=bluca@debian.org \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).