From: Akhil Goyal <gakhil@marvell.com>
To: Raja Zidane <rzidane@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [EXT] [PATCH V3] compress/mlx5: allow partial transformations support
Date: Tue, 5 Oct 2021 13:13:44 +0000 [thread overview]
Message-ID: <CO6PR18MB448452D143603865BB0EBD71D8AF9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210915001223.6238-1-rzidane@nvidia.com>
> Currently compress, decompress and dma are allowed only when all 3
> capabilities are on.
> A case where the user wants decompress offload, if decompress capability
> is on but one of compress, dma is off, is not allowed.
> Split compress/decompress/dma support check to allow partial
> transformations.
>
> V2: fix checkpatch errors
> V3: rebase.
>
> ---mlx5: replaced hardware queue object
>
> Signed-off-by: Raja Zidane <rzidane@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
This patch does not apply.
When I see in patchworks, there is another series which include this patch.
But that is also superseded and the latest series does not have this patch.
Not sure what is happening here, is this patch needed or not?
Please make sure that previous version of patches are marked as superseded.
next prev parent reply other threads:[~2021-10-05 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 14:22 [dpdk-dev] [PATCH] " Raja Zidane
2021-09-05 14:03 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-09-05 15:57 ` [dpdk-dev] [PATCH V2] " Raja Zidane
2021-09-06 19:59 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-09-15 0:12 ` [dpdk-dev] [PATCH V3] " Raja Zidane
2021-10-05 13:13 ` Akhil Goyal [this message]
2021-10-19 9:07 ` [dpdk-dev] [EXT] " Matan Azrad
2021-10-20 14:12 ` Akhil Goyal
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=CO6PR18MB448452D143603865BB0EBD71D8AF9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=rzidane@nvidia.com \
--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).