DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>, dev@dpdk.org
Cc: hemant.agrawal@nxp.com, david.marchand@redhat.com,
	hernan.vargas@intel.com
Subject: Re: [PATCH v1 3/3] baseband/acc: add support for k0 parameter
Date: Thu, 29 Aug 2024 10:01:37 +0200	[thread overview]
Message-ID: <ecd17849-685d-436a-910f-d6c5b4f56592@redhat.com> (raw)
In-Reply-To: <20240701212703.417094-4-nicolas.chautru@intel.com>



On 7/1/24 23:27, Nicolas Chautru wrote:
> The k0 may be provided to the PMD, which would be used
> as the circular buffer starting position instead of value
> which would be computed from legacy rv_index derived
> computation.
> 
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
>   drivers/baseband/acc/acc_common.h     | 6 ++++--
>   drivers/baseband/acc/rte_acc100_pmd.c | 2 +-
>   drivers/baseband/acc/rte_vrb_pmd.c    | 4 ++--
>   3 files changed, 7 insertions(+), 5 deletions(-)
> 

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Also reporting Hemant's Ack on the cover letter as patchwork doesn't
report them:
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Thanks,
Maxime


  reply	other threads:[~2024-08-29  8:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 21:27 [PATCH v1 0/3] bbdev: new " Nicolas Chautru
2024-07-01 21:27 ` [PATCH v1 1/3] bbdev: new k0 parameter for LDPC decoder operation Nicolas Chautru
2024-08-29  8:00   ` Maxime Coquelin
2024-07-01 21:27 ` [PATCH v1 2/3] test/bbdev: add support for k0 parameter Nicolas Chautru
2024-08-29  8:01   ` Maxime Coquelin
2024-07-01 21:27 ` [PATCH v1 3/3] baseband/acc: " Nicolas Chautru
2024-08-29  8:01   ` Maxime Coquelin [this message]
2024-07-02  6:50 ` [PATCH v1 0/3] bbdev: new " Hemant Agrawal
2024-09-13 13:50 ` Maxime Coquelin

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=ecd17849-685d-436a-910f-d6c5b4f56592@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=hernan.vargas@intel.com \
    --cc=nicolas.chautru@intel.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).