DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <mcoqueli@redhat.com>
To: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
Cc: Nicolas Chautru <nicolas.chautru@intel.com>,
	dev@dpdk.org, maxime.coquelin@redhat.com,
	 hemant.agrawal@nxp.com, hernan.vargas@intel.com
Subject: Re: [PATCH v1 0/2] doc: bbdev clarifications
Date: Thu, 16 Oct 2025 18:39:09 +0200	[thread overview]
Message-ID: <CAO55csxSAgO-R9djGcqJ-uegzV3cCQahR5qJ5Z6a6_+MFnAmXg@mail.gmail.com> (raw)
In-Reply-To: <edc47274-feee-4177-b973-704ce84d11e2@oss.nxp.com>

On Fri, Aug 29, 2025 at 7:08 AM Hemant Agrawal
<hemant.agrawal@oss.nxp.com> wrote:
>
> Series-
>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> On 27-08-2025 01:13, Nicolas Chautru wrote:
> > Hi,
> > Some minor clarifications to document based on
> > feedback from users.
> > Thanks
> > Nic
> >
> > Nicolas Chautru (2):
> >    doc: clarify CB vs TB level device support
> >    doc: clarify the window index usage in bbdev
> >
> >   doc/guides/bbdevs/acc100.rst        | 1 +
> >   doc/guides/bbdevs/fpga_5gnr_fec.rst | 1 +
> >   doc/guides/bbdevs/fpga_lte_fec.rst  | 1 +
> >   doc/guides/bbdevs/vrb1.rst          | 1 +
> >   doc/guides/bbdevs/vrb2.rst          | 2 ++
> >   doc/guides/prog_guide/bbdev.rst     | 7 +++++--
> >   6 files changed, 11 insertions(+), 2 deletions(-)
> >
>

Applied to next-baseband/for-main

Thanks,
Maxime


      reply	other threads:[~2025-10-16 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26 19:43 Nicolas Chautru
2025-08-26 19:43 ` [PATCH v1 1/2] doc: clarify CB vs TB level device support Nicolas Chautru
2025-10-01  8:45   ` Maxime Coquelin
2025-08-26 19:43 ` [PATCH v1 2/2] doc: clarify the window index usage in bbdev Nicolas Chautru
2025-10-02  7:45   ` Maxime Coquelin
2025-08-29  5:08 ` [PATCH v1 0/2] doc: bbdev clarifications Hemant Agrawal
2025-10-16 16: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=CAO55csxSAgO-R9djGcqJ-uegzV3cCQahR5qJ5Z6a6_+MFnAmXg@mail.gmail.com \
    --to=mcoqueli@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=hemant.agrawal@oss.nxp.com \
    --cc=hernan.vargas@intel.com \
    --cc=maxime.coquelin@redhat.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).