DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"nicolas.chautru@intel.com" <nicolas.chautru@intel.com>,
	"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
	"trix@redhat.com" <trix@redhat.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] baseband: fix drivers API
Date: Tue, 6 Oct 2020 19:42:25 +0000	[thread overview]
Message-ID: <VI1PR04MB3168625496261A212BA1D747E60D0@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201002085931.265699-1-maxime.coquelin@redhat.com>


> 
> The series prefixes drivers APIs with rte_<drv_name>_ in
> order to avoid namespace pollution.
> 
> These APIs are experimental, so no need to follow the
> deprecation process.
> 
Added Fixes commit in patch description.

Series applied to dpdk-next-crypto

Thanks.


  parent reply	other threads:[~2020-10-06 19:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  8:59 Maxime Coquelin
2020-10-02  8:59 ` [dpdk-dev] [PATCH 1/2] baseband/fpga_5gnr_fec: fix API naming Maxime Coquelin
2020-10-03 15:26   ` Tom Rix
2020-10-05  7:11     ` Maxime Coquelin
2020-10-05  7:28       ` Maxime Coquelin
2020-10-02  8:59 ` [dpdk-dev] [PATCH 2/2] baseband/fpga_lte_fec: " Maxime Coquelin
2020-10-03 15:31   ` Tom Rix
2020-10-06 19:42 ` Akhil Goyal [this message]
2020-10-07  8:22   ` [dpdk-dev] [PATCH 0/2] baseband: fix drivers API Maxime Coquelin
2020-10-07 10:09     ` Thomas Monjalon
2020-10-07 10:12       ` Maxime Coquelin
2020-10-07 10:29         ` Thomas Monjalon
2020-10-07 10:52           ` Maxime Coquelin
2020-10-07 11:06             ` Thomas Monjalon
2020-10-07 11:07               ` Thomas Monjalon
2020-10-07 12:05                 ` Akhil Goyal
2020-10-07 12:19                   ` Maxime Coquelin
2020-10-07 11:09               ` 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=VI1PR04MB3168625496261A212BA1D747E60D0@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=nicolas.chautru@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).