From: Thomas Monjalon <thomas@monjalon.net>
To: Andrey Vesnovaty <andreyv@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
asafp@nvidia.com
Subject: Re: [dpdk-dev] [PATCH 1/1] net/mlx5: fix flow shared action destroy error code
Date: Wed, 25 Nov 2020 13:58:02 +0100 [thread overview]
Message-ID: <1895206.eglvhR2BRZ@thomas> (raw)
In-Reply-To: <DM5PR1201MB2552EB6436F4AF97F05CCBC0A4FA0@DM5PR1201MB2552.namprd12.prod.outlook.com>
> > In the function rte_flow_shared_action_destroy(), the errno
> > ETOOMANYREFS has been replaced with EBUSY in the commit dc328d1c555a
> > ("ethdev: rename a flow shared action error code").
> >
> > Another occurrence of ETOOMANYREFS, added later by mistake, is replaced
> > with EBUSY errno.
> >
> > Fixes: fa7ad49e96b5 ("net/mlx5: fix shared RSS action update")
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> Reviewed-by: Tal Shnaiderman <talshn@nvidia.com>
> Tested-by: Tal Shnaiderman <talshn@nvidia.com>
Applied
prev parent reply other threads:[~2020-11-25 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 22:40 [dpdk-dev] [PATCH 1/1] net/mlx5: fix flow shared action destroy error code Thomas Monjalon
2020-11-25 5:30 ` Tal Shnaiderman
2020-11-25 12:58 ` Thomas Monjalon [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=1895206.eglvhR2BRZ@thomas \
--to=thomas@monjalon.net \
--cc=andreyv@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=talshn@nvidia.com \
--cc=viacheslavo@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.