DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Hernan Vargas <hernan.vargas@intel.com>,
	dev@dpdk.org, gakhil@marvell.com, trix@redhat.com
Cc: nicolas.chautru@intel.com, qi.z.zhang@intel.com
Subject: Re: [PATCH v2 7/7] baseband/acc: acc100 ignore missing mempools
Date: Fri, 6 Jan 2023 15:39:17 +0100	[thread overview]
Message-ID: <b5713bd3-e641-c124-d00f-3901d401ab15@redhat.com> (raw)
In-Reply-To: <20230106054443.199473-8-hernan.vargas@intel.com>



On 1/6/23 06:44, Hernan Vargas wrote:
> Mempool not strictly required to be present in op for processing.
> Previous criteria too strict. No functional impact.
> 
> Signed-off-by: Hernan Vargas <hernan.vargas@intel.com>
> ---
>   drivers/baseband/acc/rte_acc100_pmd.c | 8 --------
>   1 file changed, 8 deletions(-)
> 
> diff --git a/drivers/baseband/acc/rte_acc100_pmd.c b/drivers/baseband/acc/rte_acc100_pmd.c
> index f841b31348..b4b7418c40 100644
> --- a/drivers/baseband/acc/rte_acc100_pmd.c
> +++ b/drivers/baseband/acc/rte_acc100_pmd.c
> @@ -1832,10 +1832,6 @@ validate_enc_op(struct rte_bbdev_enc_op *op, struct acc_queue *q)
>   	if (!validate_op_required(q))
>   		return 0;
>   
> -	if (op->mempool == NULL) {
> -		rte_bbdev_log(ERR, "Invalid mempool pointer");
> -		return -1;
> -	}
>   	if (turbo_enc->input.data == NULL) {
>   		rte_bbdev_log(ERR, "Invalid input pointer");
>   		return -1;
> @@ -2679,10 +2675,6 @@ validate_dec_op(struct rte_bbdev_dec_op *op, struct acc_queue *q)
>   	if (!validate_op_required(q))
>   		return 0;
>   
> -	if (op->mempool == NULL) {
> -		rte_bbdev_log(ERR, "Invalid mempool pointer");
> -		return -1;
> -	}
>   	if (turbo_dec->input.data == NULL) {
>   		rte_bbdev_log(ERR, "Invalid input pointer");
>   		return -1;

You can also remove the mempool header include, as no mempool API is
called in this file.


      reply	other threads:[~2023-01-06 14:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06  5:44 [PATCH v2 0/7] baseband/acc: changes for 23.03 Hernan Vargas
2023-01-06  5:44 ` [PATCH v2 1/7] baseband/acc: acc100 free harq layout pointer Hernan Vargas
2023-01-06  8:53   ` Maxime Coquelin
2023-01-11 16:45     ` Vargas, Hernan
2023-01-06  5:44 ` [PATCH v2 2/7] baseband/acc: acc100 fix iteration counter in TB Hernan Vargas
2023-01-06  8:54   ` Maxime Coquelin
2023-01-06  5:44 ` [PATCH v2 3/7] baseband/acc: acc100 fix multiplexing multiple ops Hernan Vargas
2023-01-06  8:57   ` Maxime Coquelin
2023-01-06  5:44 ` [PATCH v2 4/7] baseband/acc: acc100 fix queue mapping to 64 bits Hernan Vargas
2023-01-06  9:12   ` Maxime Coquelin
2023-01-06  9:13     ` Maxime Coquelin
2023-01-06 22:06       ` Vargas, Hernan
2023-01-06  5:44 ` [PATCH v2 5/7] baseband/acc: acc100 use define constant Hernan Vargas
2023-01-06  9:13   ` Maxime Coquelin
2023-01-06  5:44 ` [PATCH v2 6/7] baseband/acc: acc100 use desc helper functions Hernan Vargas
2023-01-06 14:11   ` Maxime Coquelin
2023-01-06  5:44 ` [PATCH v2 7/7] baseband/acc: acc100 ignore missing mempools Hernan Vargas
2023-01-06 14:39   ` Maxime Coquelin [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=b5713bd3-e641-c124-d00f-3901d401ab15@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hernan.vargas@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=trix@redhat.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).