From: Akhil Goyal <akhil.goyal@nxp.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] compress/mlx5: fix assert compilation
Date: Thu, 4 Feb 2021 18:09:24 +0000 [thread overview]
Message-ID: <VI1PR04MB3168E2DD6399304B783415EDE6B39@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <DM6PR12MB375366492550A91AD5D13C0EDFB39@DM6PR12MB3753.namprd12.prod.outlook.com>
> > When ASSERT is enabled for compilation, the 2 usages of assert mechanism
> > in the driver are failed due to typos.
> >
> > Fix the typos.
> >
> > Fixes: f8c97babc9f4 ("compress/mlx5: add data-path functions")
> > Fixes: 37862dafcbed ("compress/mlx5: support 32-bit systems")
> >
> > Reported-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> > Signed-off-by: Matan Azrad <matan@nvidia.com>
> > Tested-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2021-02-04 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 9:06 Matan Azrad
2021-02-04 13:54 ` Slava Ovsiienko
2021-02-04 18:09 ` Akhil Goyal [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=VI1PR04MB3168E2DD6399304B783415EDE6B39@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=matan@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 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).