From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, Tom Rix <trix@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Liu, Tianjiao" <tianjiao.liu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add reference to bbdev companion configuration tool
Date: Thu, 12 Nov 2020 22:27:26 +0000 [thread overview]
Message-ID: <BY5PR11MB4451652BACA1FBE70CE38EE7F8E70@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <VI1PR04MB3168C5BE8C049A5464138F31E6E70@VI1PR04MB3168.eurprd04.prod.outlook.com>
> From: Akhil Goyal <akhil.goyal@nxp.com>
>
> >
> > Hi Akhil,
> > Heads up on this doc update still to be applied.
> >
>
>
> > > > doc/guides/bbdevs/acc100.rst | 19 +++++++++++++++++++
> > > > doc/guides/bbdevs/fpga_5gnr_fec.rst | 19 +++++++++++++++++++
> > > > doc/guides/bbdevs/fpga_lte_fec.rst | 19 +++++++++++++++++++
> > > > 3 files changed, 57 insertions(+)
> > > >
> > > Looks good, thanks.
> > >
> > > Reviewed-by: Tom Rix <trix@redhat.com>
> > >
> This ack is not visible in patchworks.
>
> Also the patch title is changed from the one in patchwork.
> http://patches.dpdk.org/patch/83618/
>
> Applied to dpdk-next-crypto
> Please let me know in case of any discrepancy
Looks good thanks.
prev parent reply other threads:[~2020-11-12 22:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 19:39 Nicolas Chautru
2020-11-03 19:39 ` [dpdk-dev] [PATCH v3] doc: add reference to " Nicolas Chautru
2020-11-03 19:59 ` [dpdk-dev] [PATCH v3] doc: add reference to bbdev " Tom Rix
2020-11-09 19:24 ` Chautru, Nicolas
2020-11-12 21:02 ` Akhil Goyal
2020-11-12 22:27 ` Chautru, Nicolas [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=BY5PR11MB4451652BACA1FBE70CE38EE7F8E70@BY5PR11MB4451.namprd11.prod.outlook.com \
--to=nicolas.chautru@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--cc=tianjiao.liu@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).