From: Thomas Monjalon <thomas@monjalon.net>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>
Cc: Matan Azrad <matan@nvidia.com>,
dev@dpdk.org, Asaf Penso <asafp@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix assertion check warnings
Date: Sat, 21 Nov 2020 12:36:48 +0100 [thread overview]
Message-ID: <5338789.VplnnA5vUs@thomas> (raw)
In-Reply-To: <DM6PR12MB2748EFAB31F0BCEB47565F0ACFE20@DM6PR12MB2748.namprd12.prod.outlook.com>
> > Fix assertion check warnings.
> >
> > Fixes: 8bb81f2649b1 ("net/mlx5: use thread specific flow workspace")
> >
> > Cc: stable@dpdk.org
> > Signed-off-by: Xueming Li <xuemingl@nvidia.com>
> > Reviewed-by: Slava Ovsiienko <viacheslavo@nvidia.com>
>
> Patch applied to next-net-mlx,
I know this patch is minor, but we should not write, review and apply
a fix which does not explain the issue, not even referencing the warning.
prev parent reply other threads:[~2020-11-21 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 11:01 [dpdk-dev] [PATCH] net/mlx5: fix assertion check warnings Xueming Li
2020-11-17 20:53 ` Raslan Darawsheh
2020-11-21 11:36 ` 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=5338789.VplnnA5vUs@thomas \
--to=thomas@monjalon.net \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@nvidia.com \
--cc=xuemingl@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.