From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "Rao, Nikhil" <nikhil.rao@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] eventdev: fix doxygen comment
Date: Tue, 2 Jul 2019 07:44:56 +0000 [thread overview]
Message-ID: <BYAPR18MB2424B26F3DC9D5A1F1B4736EC8F80@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1F668163772FA946975B9466A9DFF729EDE6708C@ORSMSX122.amr.corp.intel.com>
> -----Original Message-----
> From: Rao, Nikhil <nikhil.rao@intel.com>
> Sent: Tuesday, July 2, 2019 1:05 PM
> To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: [EXT] RE: [dpdk-dev] [PATCH v2] eventdev: fix doxygen comment
>
> > -----Original Message-----
> > From: jerinj@marvell.com [mailto:jerinj@marvell.com]
> > Sent: Tuesday, July 2, 2019 12:16 PM
> > To: dev@dpdk.org; Jerin Jacob <jerinj@marvell.com>
> > Cc: stable@dpdk.org; Rao, Nikhil <nikhil.rao@intel.com>
> > Subject: [dpdk-dev] [PATCH v2] eventdev: fix doxygen comment
> >
> > From: Jerin Jacob <jerinj@marvell.com>
> >
> > Update rte_eventdev.h file description to adapt to Tx adapter changes.
> >
> > Fixes: c9bf83947e2e ("eventdev: add eth Tx adapter APIs")
> > Cc: stable@dpdk.org
> > Cc: Nikhil Rao <nikhil.rao@intel.com>
> >
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> > ---
> >
> > v2:
> > - Removed refference to rte_event_eth_tx_adapter_enqueue() API and
> > made generic Tx adapter API to address
> > RTE_EVENT_ETH_TX_ADAPTER_CAP_INTERNAL_PORT
> > vs non RTE_EVENT_ETH_TX_ADAPTER_CAP_INTERNAL_PORT case(Nikhil)
> >
> > ---
> Reviewed-by: Nikhil Rao <nikhil.rao@intel.com>
Applied to dpdk-next-eventdev/master. Thanks.
prev parent reply other threads:[~2019-07-02 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 8:03 [dpdk-dev] [PATCH] " jerinj
2019-06-24 6:13 ` Rao, Nikhil
2019-07-02 6:45 ` [dpdk-dev] [PATCH v2] " jerinj
2019-07-02 7:35 ` Rao, Nikhil
2019-07-02 7:44 ` Jerin Jacob Kollanukkaran [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=BYAPR18MB2424B26F3DC9D5A1F1B4736EC8F80@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=nikhil.rao@intel.com \
--cc=stable@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).