From: David Marchand <david.marchand@redhat.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
"Chautru, Nicolas" <nicolas.chautru@intel.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Zhang, Mingshan" <mingshan.zhang@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"Vargas, Hernan" <hernan.vargas@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"trix@redhat.com" <trix@redhat.com>
Subject: Re: [PATCH v1] bbdev: add new operation for FFT processing
Date: Tue, 7 Jun 2022 13:29:57 +0200 [thread overview]
Message-ID: <CAJFAV8zbj1mZ98B3dHbd-+jC2T=RhGc-SRxnRwfCPSrUv+AtFw@mail.gmail.com> (raw)
In-Reply-To: <02d1bd6c-b86f-bf81-3fb8-c2007497c1a5@oss.nxp.com>
Hi guys,
On Thu, May 26, 2022 at 8:05 AM Hemant Agrawal
<hemant.agrawal@oss.nxp.com> wrote:
> On 5/26/2022 3:37 AM, Chautru, Nicolas wrote:
> > Hi Hernant,
> > Gentle reminder in case you can find the time. Could please have a look this patch for bbdev api extension. This is targeting 22.11.
> > New operation type for FFT processing (On top of 4 existing operations types). There is no impact to the la12xx PMD but would be good to get review/feedback.
> > This can be used for vanilla FFT and/or chained FFT/iFFT + point-wise multiplication making it applicable for SRS processing.
> > Thanks,
> > Nic
>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> HI Nicolas,
>
> Yes, I had a look into it. I see no issue in it. This is fairly
> independent feature addition to BBDEV.
>
Hemant,
For this v22.11 change, we will need some acks on the ABI breakage
announce in v22.07:
https://patchwork.dpdk.org/project/dpdk/patch/1647542252-35727-2-git-send-email-nicolas.chautru@intel.com/
Could you review it?
Thanks.
--
David Marchand
prev parent reply other threads:[~2022-06-07 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 23:49 Nicolas Chautru
2022-03-10 23:49 ` Nicolas Chautru
2022-03-11 1:12 ` Stephen Hemminger
2022-03-17 18:42 ` Chautru, Nicolas
2022-05-25 22:07 ` Chautru, Nicolas
2022-05-26 6:05 ` Hemant Agrawal
2022-06-07 11:29 ` David Marchand [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='CAJFAV8zbj1mZ98B3dHbd-+jC2T=RhGc-SRxnRwfCPSrUv+AtFw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=hernan.vargas@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=mingshan.zhang@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=thomas@monjalon.net \
--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).