From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "dave.burley@accelercomm.com" <dave.burley@accelercomm.com>
Subject: Re: [dpdk-dev] [PATCH v1] doc: update bbdev guide
Date: Tue, 6 Oct 2020 21:00:10 +0000 [thread overview]
Message-ID: <BY5PR11MB4451A8EC8F100AF26161B04EF80D0@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <VI1PR04MB316823162DDAEDA299502018E60D0@VI1PR04MB3168.eurprd04.prod.outlook.com>
Hi Akhil,
> -----Original Message-----
> From: Akhil Goyal <akhil.goyal@nxp.com>
> Sent: Tuesday, October 6, 2020 1:53 PM
> To: Chautru, Nicolas <nicolas.chautru@intel.com>; dev@dpdk.org
> Cc: dave.burley@accelercomm.com
> Subject: RE: [dpdk-dev] [PATCH v1] doc: update bbdev guide
>
> > Subject: [dpdk-dev] [PATCH v1] doc: update bbdev guide
> >
> > Clarify the capability assumptions for LLR and HARQ compression
> > format.
> > Correct one historical typo.
> >
> > Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> > ---
> Should this be cced to stable for back port?
I have no strong opinion given this is minor doc clarification update.
Also the related feature is not really exercised until 20.11 really (with new PMD).
Still if you think it is required the change would refer to that commit 3f3f608142cf48
Let me know if I should resubmit.
Thanks
Nic
next prev parent reply other threads:[~2020-10-06 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 20:58 Nicolas Chautru
2020-09-15 9:56 ` Aidan Goddard
2020-10-06 20:53 ` Akhil Goyal
2020-10-06 21:00 ` Chautru, Nicolas [this message]
2020-10-06 21:10 ` Akhil Goyal
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=BY5PR11MB4451A8EC8F100AF26161B04EF80D0@BY5PR11MB4451.namprd11.prod.outlook.com \
--to=nicolas.chautru@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dave.burley@accelercomm.com \
--cc=dev@dpdk.org \
/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).